+++ This bug was initially created as a clone of Bug #757302 +++
Description of problem:
There is a reference leak bug in python-psycopg2. Sadly, I cannot provide
narrow reproducer (without Spacewalk components).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Spacewalk nightly (PostgreSQL variant) on RHEL5 (or equivalent)
2. Create some non-empty custom channels
3. # /usr/bin/rhn-satellite-exporter --channel=parent-qrywz \
02:51:20 Gathering channel info...
Appending channels ['child-of-parent-qrywz', 'parent-qrywz']
02:51:20 Gathering binary RPM info...
python: Modules/gcmodule.c:275: visit_decref:
Assertion `gc->gc.gc_refs != 0' failed.
Export should pass.
--- Additional comment from email@example.com on 2011-11-26 03:27:14 EST ---
Created attachment 536652 [details]
--- Additional comment from firstname.lastname@example.org on 2011-11-26 03:29:17 EST ---
Created attachment 536653 [details]
A proposed patch
This problem was actually fixed in upstream. The attached please find
an equivalent of upstream's commit: eaa97def731faa6fb9b17cfe9005d327f6a70341
--- Additional comment from email@example.com on 2012-03-15 08:26:59 EDT ---
This was observed also on RHEL6 with python-psycopg2-2.0.14-1.el6_2.1
--- Additional comment from firstname.lastname@example.org on 2012-07-25 07:57:50 EDT ---
(In reply to comment #3)
> This was observed also on RHEL6 with python-psycopg2-2.0.14-1.el6_2.1
Do we have a RHEL 6 version of this bugzilla?
--- Additional comment from email@example.com on 2012-07-25 11:15:15 EDT ---
I don't work with the Python CAPI but a quick look at the patch seems sane. I also checked that
* This is the only difference between typecast.c in 2.0.14 and typecast.c at the time of the upstream commit.
* The patch is still applied in upstream's current 2.4.4 release.
Devrim, I'll go ahead and apply and build tomorrow unless I hear otherwise from you.
The change fixed the issues for the EPEL 5's python-psycopg2 package. It would be great to see it in RHEL 6 as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.