[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: Hey, the problem normalized after installing the newest version of cryptography, with which I could reproduce the same problem too. It turned out that asn1crypto wasn't even needed in my project. Sorry for the inconvenience, and thank you for your help.

[issue38814] Python3.7.5 crashes on OSX with my django project

Ned Deily added the comment: Sorry, we have strayed from dealing with a Python issue here so, if you need nore assistance, you really should seek help elsewhere. But a quick web search found this which seems to describe your problem: https://github.com/wbond/asn1crypto/issues/113

[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: Upon reinstalling openssl with homebrew, I get the following info: -- openssl is keg-only, which means it was not symlinked into /usr/local, because Apple has deprecated use of OpenSSL in favor of its own TLS and crypto libraries. If you need to

[issue38814] Python3.7.5 crashes on OSX with my django project

Ned Deily added the comment: Almost any kind of crash is possible when using ctypes. But you almost certainly don't want to be loading /usr/lib/libcrypto.dylib. That's the macOS legacy version which is there only for legacy Apple-supplied third-party components, like the Apple-supplie

[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: Here's an md5sum of /usr/lib/libcrypto.dylib: MD5 (/usr/lib/libcrypto.dylib) = d19ca8b227c32d30f92ed0665dfe73d0 -- ___ Python tracker ___

[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: As I'm triangulating the problem down, I can now reproduce the problem without running django: python -X faulthandler -c 'from asn1crypto._perf import _big_num_ctypes' gives the output: Fatal Python error: Aborted Current thread 0x000117155dc0 (most

[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: So after making the changes, recompiling everything and using `python -X faulthandler backend/manage.py runserver --nothreading --noasgi --noreload` to start django without the autoreloader that hides the crashed process' output, here's what I get: File

[issue38814] Python3.7.5 crashes on OSX with my django project

Ned Deily added the comment: The stack track is pretty suspicious. I really don't know why it would be crashing where it shows which seems to be pretty early in the interpreter. If you haven't already, you might just want to try reinstalling from Homebrew first and try again. If you do

[issue38814] Python3.7.5 crashes on OSX with my django project

Change by Ned Deily : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38814] Python3.7.5 crashes on OSX with my django project

László Károlyi added the comment: Hello, the only C extension I use is xapian and mysql (with mariadb), xapian comes from their own git repo, and mariadb comes from mysqlclient, both (and everything else I don't know about) compile with the python 3.7.5 I installed within a venv. I'll try

[issue38814] Python3.7.5 crashes on OSX with my django project

Ned Deily added the comment: Sorry but with a non-debug build of Python, it's not very likely someone would be able to glean much from the macOS crash stack trace here. You also seem to have a very large number of C extension modules, some apparently from Homebrew and others from other

[issue38814] Python3.7.5 crashes on OSX with my django project

New submission from László Károlyi : Hey, I have a huge Django project that starts up fine with the dev server on Linux and in production that is also Linux. Whenever I try to start it on my OSX, the python process crashes with a SIGABRT and I get a crash window from OSX. I use homebrew with