[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

[Antoine Pitrou]

Antoine Pitrou added the comment:

Well, the error message comes from a misuse of the PyEval_RestoreThread() (by passing it a NULL argument), either directly or by using another API such as Py_END_ALLOW_THREADS which calls that function. The problem is likely to be in the Solidoodle extension. Whatever the source of the problem, though, only a low-level C traceback would allow to tell.

I agree with closing, stock Python is very unlikely to produce such tracebacks.

----------
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16749>
_______________________________________