Thanks for the thoughts - much appreciated! The threaded super-goat
was indeed the offender. A very aggressive QA tester got us enough of
a pattern to identify the offending module: pyOpenSSL. After looking
at it closely, we found there are problems with its thread handling.
In particular, the
On Nov 17, 10:34 am, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi folks - wondering if anyone has any pointers on troubleshooting
garbage collection. My colleagues and I are running into an
interesting problem:
Intermittently, we get into a situation where the garbage collection
code is
dave..mail.com (Dave) wrote:
8- description of horrible problem --
Faced with this, I would:
1 - identify the modules that import gc to separate the
sheep from the goats.
2 - do my best to change gc importing goats back to sheep.
3 - amongst the remaining goats,
Hi folks - wondering if anyone has any pointers on troubleshooting
garbage collection. My colleagues and I are running into an
interesting problem:
Intermittently, we get into a situation where the garbage collection
code is running in an infinite loop. The data structures within the
garbage
