-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault during the test__xxsubinterpreters test #100981
Comments
BTW, I have to specify "-F" to run the test indefinitely otherwise it's really hard to catch with a single invocation of the test. Also, "-j4" seems to be accelerate the crash, since with "-j0" it runs quite a few successful passes before crashing:
I also noticed that load average is climbing up despite that noting else is occupying the machine (OK, this is expected, it seems, the number should be close to the number of children). If I run the test with "-j1" (just one child process) then either I am not patient enough or it seems that it does not crash in that scenario:
|
Seems similar to or at least related to #100711. |
@galaxy4public, do you still get the failure with gh-101431 applied? |
@ericsnowcurrently, unfortunately, I don't have enough knowledge for backporting the mentioned commit to the latest released version of Python (which is 3.11.2) and I cannot proceed with the bleeding edge, so it seems I cannot test the fix :(. |
Can you verify if this is fixed now? This may have been a case of gh-104341. |
Closing as |
Crash report
When running the testsuite one test is intermittently failing with a segmentation fault. The test in question is test=test__xxsubinterpreters and the crash seems to be GIL related. I am able to consistently reproduce the crash on my environment where I am building Python inside a chroot (/proc, /sys, and /dev are "mount --bind"ed from the host system).
On a freshly built with GCC 12.2.0 Python 3.11 with the following configure options:
This is the testsuite output with just the test in question:
Error messages
I acquired a core dump and under gdb it looks as follows:
Your environment
The text was updated successfully, but these errors were encountered: