After #18334, a "while condition: pass" in a thread will preclude releasing the GIL, hanging the program with CPU at 100%.

Trivial to reproduce:

"""
#!/usr/bin/env python3.10

import threading
import time

def worker():
    while cont:
        pass

def main():
    global cont
    cont = True
    t = threading.Thread(target=worker)
    t.start()
    time.sleep(1)
    cont = False
    t.join()

if __name__ == '__main__':
    main()
"""

#18334 assumes that since all loops will contain a backwards edge, checking for interrupts on JUMP_ABSOLUTE should be sufficient.

However, #23743 changed the back edges in while statements. So worker compiles to:

2 0 LOAD_GLOBAL 0 (cont)
2 POP_JUMP_IF_FALSE 7 (to 14)

3 >> 4 NOP

2 6 LOAD_GLOBAL 0 (cont)
8 POP_JUMP_IF_TRUE 2 (to 4)
10 LOAD_CONST 0 (None)
12 RETURN_VALUE
>> 14 LOAD_CONST 0 (None)
16 RETURN_VALUE

which has no CALL or JUMP_ABSOLUTE instructions.

New changeset 000e70a by Mark Shannon in branch 'main':
bpo-44645: Check for interrupts on any potentially backwards edge. (GH-27167)
000e70a

New changeset 0e349ea by Mark Shannon in branch '3.10':
[3.10] bpo-44645: Check for interrupts on any potentially backwards edge. (GH-27167) (GH-27183)
0e349ea

PR 27167 hangs or fails. in the refleak buildbots, so I am going to proceed to revert

To reproduce the problem:

$./python -m test test_threading -R : -v

...

test_original_excepthook (test.test_threading.ExceptHookTests) ... ok
test_system_exit (test.test_threading.ExceptHookTests) ... ok
test_can_interrupt_tight_loops (test.test_threading.InterruptMainTests) ...

(HANGS here or some time fails like in:

======================================================================
FAIL: test_can_interrupt_tight_loops (test.test_threading.InterruptMainTests)
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/home/buildbot/buildarea/pull_request.cstratak-RHEL7-ppc64le.refleak/build/Lib/test/support/threading_helper.py", line 62, in decorator
    return func(*args)
           ^^^^^^^^^^^
  File "/home/buildbot/buildarea/pull_request.cstratak-RHEL7-ppc64le.refleak/build/Lib/test/test_threading.py", line 1630, in test_can_interrupt_tight_loops
    self.assertNotEqual(iterations, 0)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 0 == 0

https://buildbot.python.org/all/#/builders/411/builds/92

New changeset c90c591 by Pablo Galindo Salgado in branch 'main':
Revert "bpo-44645: Check for interrupts on any potentially backwards edge. (GH-27167)" (bpo-27194)
c90c591

New changeset 42a5514 by Miss Islington (bot) in branch '3.10':
Revert "bpo-44645: Check for interrupts on any potentially backwards edge. (GH-27167)" (GH-27194) (bpo-27195)
42a5514

Can we at least include the fix, until we can come up with a better test?

That test fails on 3.9 as well as 3.10 and main.

With a 3.9 build and the test in bpo-27194:

./python -m test test_threading -R :
0:00:00 load avg: 0.95 Run tests sequentially
0:00:00 load avg: 0.95 [1/1] test_threading
beginning 9 repetitions
123456789
...test test_threading failed -- Traceback (most recent call last):
  File "/home/mark/repos/cpython/Lib/test/test_threading.py", line 1479, in test_can_interrupt_tight_loops
    self.assertNotEqual(iterations, 0)
AssertionError: 0 == 0

I don't know what the underlying issue is.

Can you observe a failure without the -R flag?

New changeset d09c134 by Mark Shannon in branch 'main':
bpo-44645: Check for interrupts on any potentially backwards edge (GH-27216)
d09c134

New changeset 37bdd22 by Miss Islington (bot) in branch '3.10':
bpo-44645: Check for interrupts on any potentially backwards edge (GH-27216) (GH-27235)
37bdd22