[issue27468] Erroneous memory behaviour for objects created in another thread

Changes by Emanuel Barry : -- resolution: -> not a bug stage: -> resolved ___ Python tracker ___

[issue27468] Erroneous memory behaviour for objects created in another thread

Adria Garriga added the comment: Yes, that seems to be it. Storing info in the Thread object is just for the sake of keeping the example short, but the error is the same you pointed out. Thank you very much and I hope I didn't waste too much of your time! -- status: open -> closed

[issue27468] Erroneous memory behaviour for objects created in another thread

Peter Otten added the comment: Your code relies on the assumption that when the lambda is invoked the global t is still bound to the Thread instance you are starting. It seems that this is not always the case, and I don't see why it should be guaranteed either. I don't know whether it's a good

[issue27468] Erroneous memory behaviour for objects created in another thread

New submission from Adria Garriga: I create several objects in the main thread, and then spawn several threads that "take ownership" of one object each. Within that thread, the objects' attributes' values are not consistent. The bug only happens sometimes. from threading import Thread import

[issue27468] Erroneous memory behaviour for objects created in another thread

Changes by Adria Garriga : Removed file: http://bugs.python.org/file43663/test.py ___ Python tracker ___