[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-10-18 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread STINNER Victor
STINNER Victor added the comment: > Thanks for the reply, I don't know exactly what you mean by making a simpler > reproducer Script with less lines and less imports. > just using pip will cause this issue to happen from time to time, which is > why I find it unlikely to be caused by third

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread axel
axel added the comment: Thanks for the reply, I don't know exactly what you mean by making a simpler reproducer, but as I wrote in the original post, just using pip will cause this issue to happen from time to time, which is why I find it unlikely to be caused by third party libs. I will

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread STINNER Victor
STINNER Victor added the comment: > Also, it would help a lot to use a Python built in debug mode. See: https://pythondev.readthedocs.io/builds.html#pydebug -- ___ Python tracker

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread STINNER Victor
STINNER Victor added the comment: Also, it would help a lot to use a Python built in debug mode. -- ___ Python tracker ___ ___

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread STINNER Victor
STINNER Victor added the comment: This is very likely a crash in a 3rd party C extensions. You should try to write a simpler reproducer and report it to the C extensions causing the crash. You can try to enable the Python Development Mode to see if it provides you more information:

[issue43668] Segfault with for fresh ubuntu 20.04 install

2021-03-30 Thread axel
New submission from axel : The python interpreter segfaults when running in a miniconda environment on a fresh install of ubuntu 20.04.2. This seems to happen intermittently, both while running "pip" during the conda setup of an environment and during the execution of code like below. The