-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Trying to start a new process crashes the Python interpreter on FreeBSD 12 #1411
Copy link
Copy link
Closed
Labels
bugtypetypecriticalprocess dies, hangs forever, or memory is corrupt: segfault, deadlock, double free, crash on importprocess dies, hangs forever, or memory is corrupt: segfault, deadlock, double free, crash on importfreebsdplatform : FreeBSD specificplatform : FreeBSD specificmemleakmemory is leaked at the C level: a refcount never released, memory not freed, ...memory is leaked at the C level: a refcount never released, memory not freed, ...
Description
Activity
Metadata
Metadata
Assignees
Labels
bugtypetypecriticalprocess dies, hangs forever, or memory is corrupt: segfault, deadlock, double free, crash on importprocess dies, hangs forever, or memory is corrupt: segfault, deadlock, double free, crash on importfreebsdplatform : FreeBSD specificplatform : FreeBSD specificmemleakmemory is leaked at the C level: a refcount never released, memory not freed, ...memory is leaked at the C level: a refcount never released, memory not freed, ...
Software versions:
Python: 3.7.2
FreeBSD: 12.0-RELEASE r341666
Psutil: 5.5.0
Trying to use psutil.Popen() leads to the Python interpreter crashing on FreeBSD 12.
For example, trying to start the echo executable leads to the result below:

If I try to start wget, the interpreter doesn't crash right away sometimes. A stack trace is also sometimes printed (I had to try this on Python 3.6 to trigger it):
