[issue34087] Segmentation fault on visit_decref

STINNER Victor added the comment: Please try to set PYTHONMALLOC=debug environment variable and run again your test. I hope that Python will be able to catch a memory corruption somewhere. If it's the case, you can try: PYTHONMALLOC=debug python3 -X tracemalloc=10 (...) To see where the cor

[issue34087] Segmentation fault on visit_decref

Rodrigo Pinheiro Marques de Araújo added the comment: Running with `-X faulthandler` Fatal Python error: Segmentation fault Current thread 0x7fff89cf2380 (most recent call first): File "/Users/rodrigo/root/lib/python3.7/site-packages/django/urls/resolvers.py", line 526 in resolve

[issue34087] Segmentation fault on visit_decref

INADA Naoki added the comment: If example cannot be small, you can share the project on Github or other place. If your project is private, you can create OSS version of reproducer. If you can't create OSS reproducer, we can't debug it. 3rd party library list may helpful, but I'm not sure. ---

[issue34087] Segmentation fault on visit_decref

Rodrigo Pinheiro Marques de Araújo added the comment: Sorry for that. I’m not able to make a little example to reproduce this bug. It’s happens during Django tests on a very large code base. A interest thing is that not happens with “-X dev” parameters. Please, any suggestions how I can get m

[issue34087] Segmentation fault on visit_decref

INADA Naoki added the comment: It's difficult to investigate without reproducible example. Do you use 3rd party extension module? Typical cause of these crash is bug in 3rd party extensions. -- nosy: +inada.naoki ___ Python tracker

[issue34087] Segmentation fault on visit_decref

New submission from Rodrigo Pinheiro Marques de Araújo : * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x656d6f6e2236) frame #0: 0x00010014c819 python3`visit_decref(op=0x656d6f6e222e, data=0x) at gcmodule.c:271 [opt] 2