[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Mark Shannon added the comment: Please leave the issue open. This is a real bug. It may not be fixed right now, but that doesn't mean it won't ever be fixed. -- nosy: +Mark.Shannon ___ Python tracker

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Xinmeng Xia added the comment: It seems that this bug won't be fixed. Should this issue be closed now? -- ___ Python tracker ___

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Xinmeng Xia added the comment: Thank you for your patient reply. I see now. Hoping that some one can figure out a good idea to fix this problem. -- ___ Python tracker ___

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Steve Stagg added the comment: It's one of those ugly multithreading issues that's really hard to reason about unfortunately. In this case, it's not the size of the loop so much as you've discovered a way to make it very likely that the background thread is doing IO (and holding the IO

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Xinmeng Xia added the comment: Could we try to limit the number of thread or state or something? I mean if we set parameter of "range", for example, to 1000 or less here, the crash will no longer happen. I think the parser can not handle too heavy loop so that it crashes. --

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Steve Stagg added the comment: I think the problem here is that the issue can only really be detected late on during interpreter shutdown. This makes recovery very hard to do. Plus the thread termination has left shared state in an unmanaged condition, so it's super dangerous to re-enter

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Xinmeng Xia added the comment: Thanks for your kind explanation! Now, I have understand the causes of this core dump. Considering it will not cause core dump in Python 2.x, I am wondering should we suggest an exception to catch it rather than "core dump"? --

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

Steve Stagg added the comment: Minimal test case: import sys, threading def run(): for i in range(1000): sys.stderr.write(' =.= ') if __name__ == '__main__': threading.Thread(target=run, daemon=True).start() === I think this is expected behaviour. My knowledge

[issue42717] The python interpreter crashed with "_enter_buffered_busy"

New submission from Xinmeng Xia : The following program can work well in Python 2. However it crashes in Python 3( 3.6-3.10 ) with the following error messages. Program: import sys,time, threading class test: def test(self): pass