This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients amaury.forgeotdarc, jnoller, mark.dickinson
Date 2008-08-01.14:31:25
SpamBayes Score 0.02706034
Marked as misclassified No
Message-id <1217601086.05.0.946018914061.issue3399@psf.upfronthosting.co.za>
In-reply-to
Content
> This is wrong (the GIL must be held when using the PyMem_* and
> PyObject_* functions), and is probably the cause of the failed 
assertion.

This sounds quite likely.

I just managed (using the low-tech method of setting a static variable 
on entry and clearing it on exit) to confirm that PyObject_Malloc in 
obmalloc.c is being accessed simultaneously by multiple threads when
test_multiprocessing is run.
History
Date User Action Args
2008-08-01 14:31:26mark.dickinsonsetrecipients: + mark.dickinson, amaury.forgeotdarc, jnoller
2008-08-01 14:31:26mark.dickinsonsetmessageid: <1217601086.05.0.946018914061.issue3399@psf.upfronthosting.co.za>
2008-08-01 14:31:25mark.dickinsonlinkissue3399 messages
2008-08-01 14:31:25mark.dickinsoncreate