[pypy-issue] [issue799] Strange exception with threads

[Armin Rigo]

Armin Rigo <armin.rigo at gmail.com> added the comment:

Fixed (took me the day).  It was caused by the lock's interp-level destructor
releasing the GIL, which is now fixed and checked not to occur (I had to fix a
number of other __del__s too).

For reference:

- thread 2 calls gc.collect() at a completely random point
- it calls the destructors
- it releases the GIL
- thread 1 run
- thread 1 sees a random state and crashes

----------
nosy: +arigo
status: unread -> resolved

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue799>
________________________________________