[issue46070] broken subinterpreters

STINNER Victor added the comment: Using attached bug.py, it's possible to trigger the crash on the main branch. I modified the reproducer to use the "_asyncio" extension which still uses the old API PyModule_Create() with PyModuleDef.m_size = -1. -- Added file: https://bugs.python.or

[issue46070] broken subinterpreters

STINNER Victor added the comment: I can sometimes reproduce the crash on Windows with Python 3.9. Call stack (most recent to oldest frames): * PyObject_GC_UnTrack() - crash on _PyGCHead_SET_NEXT(prev, next) because prev is dangling pointer (0x1fe64dd5250), Visual Studio is unable to read mem

[issue46070] broken subinterpreters

Ben Steffensmeier added the comment: We have been seeing intermittent crashes on jep that we tracked down to the same change (d0d29655ff). I have created a sample program using _testcapi that crashes about 50% of the time when run on Windows with Python 3.9.9. We have not been able to reprod

[issue46070] broken subinterpreters

Change by Nathan Jensen : -- nosy: +ndjensen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue46070] broken subinterpreters

Petr Viktorin added the comment: That was a fix for GH-17350, which might need to be reverted as well. Victor, could you take another look at GH-17350? I must admit I (still) don't understand this change; what would break if it was reverted (along with the fixup from bpo-44050)? --

[issue46070] broken subinterpreters

graysky added the comment: While this is being evaluated, can someone give an opinion about the sanity of simply reverting https://hg.python.org/lookup/d0d29655ff for now in order to use 3.10.1? Thanks. -- ___ Python tracker

[issue46070] broken subinterpreters

graysky added the comment: @Eric - I have not seen this on 3.8 or 3.9. No data before 3.8. -- ___ Python tracker ___ ___ Python-bu

[issue46070] broken subinterpreters

Petr Viktorin added the comment: Interned strings were broken in GH-20058, see bpo-46006. Maybe that's also the issue here? -- nosy: +vstinner ___ Python tracker ___

[issue46070] broken subinterpreters

Eric Snow added the comment: (related: bpo-44059) Presumably the problem relates to global state used in different interpreters leading to an inconsistent state in the crashing extension (or its dependencies). @graysky, do you know if this was a problem before Python 3.8? -- compon

[issue46070] broken subinterpreters

New submission from graysky : Seems as though cpython is broken when working with subinterpreters. The problematic change could be (d0d29655ff) affecting import.c.[1] Reverting this commit and rebuilding python fixes the issues on my system with some scripts that import sqlite, for example, t