Issue 31962: test_importlib double free or corruption (original) (raw)

On a Raspberry Pi 3 running

Linux pi3 4.9.58-v7+ #1046 SMP Tue Oct 24 17:07:15 BST 2017 armv7l GNU/Linux

C(PP)FLAGS="-O6 -march=armv8-a+crc -mtune=cortex-a53 -mfpu=crypto-neon-fp-armv8 -mfloat-abi=hard -ftree-vectorize"

Built with ./configure --enable-loadable-sqlite-extensions --enable-optimizations --disable-shared --with-lto --enable-ipv6 --with-threads

When the build phase is ... Running code to generate profile data (this can take a while): make run_profile_task make[1]: Entering directory '/home/pi/Downloads/Python-3.6.3' : # FIXME: can't run for a cross build ./python -m test.regrtest --pgo || true Run tests sequentially ...

It errors and dies with 0:23:56 load avg: 0.87 [176/405] test_importlib *** Error in `./python': double free or corruption (!prev): 0x014166e0 *** Fatal Python error: Aborted

Thread 0x685ff460 (most recent call first): File "", line 98 in acquire File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 83 in _acquire File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 93 in f File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 38 in task

Thread 0x76f04000 (most recent call first): File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 17 in _wait File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 56 in wait_for_finished File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 99 in run_deadlock_avoidance_test File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 113 in test_no_deadlock File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/case.py", line 605 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/case.py", line 653 in call File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in call File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in call File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in call File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in call File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in call File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/init.py", line 1765 in run File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/init.py", line 1889 in _run_suite File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/init.py", line 1933 in run_unittest File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 172 in test_runner File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 173 in runtest_inner File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 137 in runtest File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 378 in run_tests_sequential File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 457 in run_tests File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 535 in _main File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 509 in main File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 584 in main File "/home/pi/Downloads/Python-3.6.3/Lib/test/regrtest.py", line 46 in _main File "/home/pi/Downloads/Python-3.6.3/Lib/test/regrtest.py", line 50 in File "/home/pi/Downloads/Python-3.6.3/Lib/runpy.py", line 85 in _run_code File "/home/pi/Downloads/Python-3.6.3/Lib/runpy.py", line 193 in _run_module_as_main Aborted

Every time. These exact same parameters and flags worked with 3.6.2 with no issue, but they die on 3.6.3

I close the issue as out of date, since there is no activity for 4 years. Maybe it was fixed in the meanwhile.

If it's not the case, please reopen the issue. If someone can still reproduce the issue, it would help to write a short reproducer script based on the test causing the crash.