Rodrigo Pinheiro Marques de Araújo added the comment:
I can reproduce the segmentation fault using 'testproj.tar.gz' with homebrew
and compiled from source. MacOS X High Sierra 10.13.5 (17F77).
--
___
Python tracker
<https://bu
Rodrigo Pinheiro Marques de Araújo added the comment:
I did remove PyYAML, lxml and Pillow here but segfault still happen
--
___
Python tracker
<https://bugs.python.org/issue34
Rodrigo Pinheiro Marques de Araújo added the comment:
Extensions:
./_cffi_backend.cpython-37m-darwin.so
./_mssql.cpython-37m-darwin.so
./_yaml.cpython-37m-darwin.so
./Crypto/Cipher/_AES.cpython-37m-darwin.so
./Crypto/Cipher/_ARC2.cpython-37m-darwin.so
./Crypto/Cipher/_ARC4.cpython-37m
Rodrigo Pinheiro Marques de Araújo added the comment:
Unfortunately with 'PYTHONMALLOC=debug' the segmentation fault do not happen.
--
___
Python tracker
<https://bugs.python.o
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
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
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.
