[issue24605] segmentation fault at asciilib_split_char.lto_priv

Change by STINNER Victor : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue24605] segmentation fault at asciilib_split_char.lto_priv

STINNER Victor added the comment: No activity for 6 years, the reporter didn't provide any way to reproduce the crash, I close the issue. Note: Python 3.10 now dumps the list of third party C extensions on a fatal error, or when faulthandler handlers a crash ;-) Just enabled the Python Deve

[issue24605] segmentation fault at asciilib_split_char.lto_priv

Irit Katriel added the comment: Is there anything we can do about this or should it be closed? -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___ ___

[issue24605] segmentation fault at asciilib_split_char.lto_priv

STINNER Victor added the comment: You have to search for memory corruptions. You can try to run your application with a Python compiled a debug mode. If it doesn't work, you may try Valgrind which require a Python compiled with --with-valgrind and to use the suppression file. See Misc/README.v

[issue24605] segmentation fault at asciilib_split_char.lto_priv

josch added the comment: I do not see any module implemented in C in the imports. Is there a way to find out from where the segmentation fault came? -- ___ Python tracker ___ __

[issue24605] segmentation fault at asciilib_split_char.lto_priv

STINNER Victor added the comment: Oh, networkx looks to be written in pure Python. You should search for a module implemented in C. -- ___ Python tracker ___ ___

[issue24605] segmentation fault at asciilib_split_char.lto_priv

STINNER Victor added the comment: It looks more like a bug in networkx, than a bug in Python itself. networkx has probably issues with reference counter, concurrency (threads), or things like that. I'm unable to reproduce the crash on Python 3.4 (system binary from Fedora 22) or Python 3.6 (c

[issue24605] segmentation fault at asciilib_split_char.lto_priv

New submission from josch: Hi, sometimes (but not reliably reproducibly, one has to run it a few times) I get a segmentation fault when running the following networkx based Python code on large input graphs: https://gitlab.mister-muffin.de/debian-bootstrap/botch/blob/master/tools/graph-differ