[issue3200] Python's crash in heavy multithreading IO operations

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Closing as "already resolved in the upcoming release" -- status: pending -> closed ___ Python tracker <[EMAIL PROTECTED]> __

[issue3200] Python's crash in heavy multithreading IO operations

Eric Sadit <[EMAIL PROTECTED]> added the comment: #!/usr/bin/python import sys import thread f = file("o.test","w") buff = " " * 1024 def run(): while 1: try: f.read(100) # f.write(buff) except Exception, e: print >>sys.stderr, "An except

[issue3200] Python's crash in heavy multithreading IO operations

Eric Sadit <[EMAIL PROTECTED]> added the comment: The test script #!/usr/bin/python import sys import thread f = file("o.test","w") buff = " " * 1024 def run(): while 1: try: f.read(100) # f.write(buff) except Exception, e: print >>sys.s

[issue3200] Python's crash in heavy multithreading IO operations

Eric Sadit <[EMAIL PROTECTED]> added the comment: Thanks Amaury I run a test script and Python 2.5.2 crashes, but 2.6b1 runs perfectly throwing a ValueError exception (Operation of closed file) in the reader/writer thread and "IOError: close() called during concurrent operation on the same file

[issue3200] Python's crash in heavy multithreading IO operations

Eric Sadit <[EMAIL PROTECTED]> added the comment: Ok, I will try to reproduce it in the python 2.6b1 version, and I report to you the result Saludos On Wed, Jun 25, 2008 at 12:44 PM, Amaury Forgeot d'Arc < [EMAIL PROTECTED]> wrote: > > Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment

[issue3200] Python's crash in heavy multithreading IO operations

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: This problem may be a duplicate of issue815646 and issue595601, and was probably corrected with r62195. Can you please check with the new python version 2.6b1 ? -- nosy: +amaury.forgeotdarc resolution: -> out of date status: o

[issue3200] Python's crash in heavy multithreading IO operations

New submission from Eric Sadit <[EMAIL PROTECTED]>: Hello, I found a rare bug in heavy multithreading IO operations. The bug arises under a stupid sequence of I/O operations. The sequence is not a normal one, but the real problem is that the Python's interpreter crashes. The correct behavior sho