Re: visit_decref: Assertion `gc->gc.gc_refs != 0' failed.

On 23/03/10 16:39, Michael Tharp wrote:
> Seeing python bomb out on a GC-related assertion during some heavy load
> testing:
>
> #3 0x000000000048bd2c in visit_decref (op=0x7f7b78037c58,
> data=<value optimized out>) at Modules/gcmodule.c:275
> __PRETTY_FUNCTION__ = "visit_decref"
>
> (gdb) p op->ob_type->tp_name
> $3 = 0x7f7b7fb16398 "psycopg2._psycopg.type"
>
> It always happens eventually, although it takes anywhere from a few
> minutes to two hours to trigger. I've seen it in these configurations:

Hi,

could you provide a self-contained test case? I'm getting a very similar 
segfault and I'm not sure it's because of my patches to psycopg2 or 
would this happen in a vanilla build as well (I'm pretty sure it's my 
fault, though...).

But anyway, if it's happening in a vanilla release of psycopg2 It'd be 
interesting to try and reproduce it.

Cheers,
Jan