[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: The initial issue has been fixed by a revert. Let's continue the discussion on bpo-36818 to maybe reapply commit 396e0a8d9dc65453cb9d53500d0a620602656cfe. -- resolution: -> fixed stage: -> resolved status: open -> closed __

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: > commit 396e0a8d9dc65453cb9d53500d0a620602656cfe (refs/bisect/bad) Extract of this change: static inline void -exit_thread_if_finalizing(_PyRuntimeState *runtime, PyThreadState *tstate) +exit_thread_if_finalizing(PyThreadState *tstate) { +_PyRuntimeSt

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: I used git bisect and I found: commit 396e0a8d9dc65453cb9d53500d0a620602656cfe (refs/bisect/bad) Author: Eric Snow Date: Fri May 31 21:16:47 2019 -0600 bpo-36818: Add PyInterpreterState.runtime field. (gh-13129) stress.py starts to crash at this c

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: If you apply attached sleep_at_exit.patch and run attach stress.py, you should quickly get a crash: $ git apply sleep_at_exit.patch $ make && ./python stress.py Segmentation fault (core dumped) That's a simplified example of the multiprocessing crash.

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Change by STINNER Victor : Added file: https://bugs.python.org/file48387/stress.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Pablo Galindo Salgado added the comment: Note that the core dump that we are talking about is something that we produced afterwards when trying to reproduce the issue. The core that is produced as part of the tests could be different. I am trying to get access to the test files. --

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: I marked bpo-37143 "multiprocessing crashed with EXCEPTION_ACCESS_VIOLATION on Python on x86 Windows7 3.x" as a duplicate of this issue. Even if bpo-37143 looks very different (crash in a different file, on a different operating system), I'm now quite sure t

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: I looked at the coredump with Pablo. In short, the main thread is calling Py_Exit() to exit the process and so released memory, and a daemon thread does crash on calling PyEval_RestoreThread() because tstate memory was freed. The question is now if this bug

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Pablo Galindo Salgado added the comment: CURRENT-amd64% lldb ./python -c python.core (lldb) target create "./python" --core "python.core" Core file '/home/pablo/cpython/python.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'python', stop reason = signal SIGBUS * frame #0: 0x

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: > FTR Victor reverted GH-13714 that triggers this. Sadly, this revert wasn't enough. New fresh coredump on "AMD64 FreeBSD CURRENT Shared 3.x": https://buildbot.python.org/all/#builders/168/builds/1145 Warning -- Dangling processes: {} Warning -- Dangling pro

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Pablo Galindo Salgado added the comment: > FTR Victor reverted GH-13714 that triggers this. Given the nature of the bugs, I would recommend to watch the buildbots -- ___ Python tracker _

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Łukasz Langa added the comment: FTR Victor reverted GH-13714 that triggers this. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Pablo Galindo Salgado added the comment: Adding the release manager to consider this -- nosy: +lukasz.langa ___ Python tracker ___

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: https://bugs.python.org/issue33608#msg340075: > My procedure to reproduce the crash on FreeBSD: > https://bugs.python.org/issue36114#msg337092 I ran this test for 20 min on the FreeBSD CURRENT buildbot: I failed to reproduce the bug. -- ___

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Pablo Galindo Salgado added the comment: I am unable to reproduce this locally, will post here a backtrace if I manage to do so. -- ___ Python tracker ___ ___

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Antoine Pitrou added the comment: Would be nice if someone could post a gdb backtrace of the core dump. -- ___ Python tracker ___ _

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: Maybe it's related to bpo-33608. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: New coredump: https://buildbot.python.org/all/#builders/168/builds/1129 -- nosy: +vstinner ___ Python tracker ___ ___

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Change by Pablo Galindo Salgado : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

Change by Pablo Galindo Salgado : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

New submission from Pablo Galindo Salgado : test_import (test.test_multiprocessing_spawn._TestImportStar) ... ok -- Ran 352 tests in 322.667s OK (skipped=34) Warning -- files was modified by test_multiprocessing_spawn Before: