[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

STINNER Victor added the comment: I'm unable to reproduce the crash on Fedora 31. A crash during a garbage collection usually means that there is a corrupted object somewhere, and suddenly, we discover the inconsistent. The crash can be far from where the inconsistency was created. You may

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Tim Peters added the comment: I haven't used protobuf, but it's _generally_ true that crashes that occur for the first time in the presence of C or C++ extension modules are due to subtle (or not so subtle) mistakes in using the sometimes-delicate Python C API. So it's too soon to play

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Timothy Lusk added the comment: I'll admit I don't know enough about Python c extensions to make that call, but the fact that it wasn't crashing in the protobuf extension itself during the import but instead during the next garbage collection made me believe it was a Python bug. Maybe

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Change by Benjamin Peterson : -- status: -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Benjamin Peterson added the comment: Could also be a bug in however protobuf handles exceptions on module initialization. -- ___ Python tracker ___

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Timothy Lusk added the comment: I've realized this might not be Python 3.7 specific, the reason protobuf is throwing an exception during import in my above example (as well as in our application) is because it's throwing a deprecation warning that was only introduced in 3.7. Python 3.6

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

Tim Lusk added the comment: Alright I was finally able to reproduce the issue with a small code snip and capture the stack in gdb. It looks like the issue has something to do with an exception thrown while importing a class (and possibly only when the class is a c_ext, but I haven't

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

New submission from Tim Lusk : I'm working on porting an application from Python 3.6.8 to 3.7.3 and am running into this segfault. I'm not able to pin point exactly what Python code is causing this as it's a very large enterprise application and I can't seem to pinpoint exactly where this is