Terminal messed up after Python (native module) crash

[domdfcoding]

If a Python native module crashes the interpreter (I'm seeing this with just-playback on CPUs without AVX2, but any native module crash that causes a Fatal Python Error will do the same) the terminal is filled with characters like 51;104;36M51... every time the mouse moves, and I can't highlight or scroll. I assume textual is not properly cleaning up when Python crashes like this. I don't know how to actually get cleanup code to run though - atexit seems to get bypassed.

reset does fix the terminal though.

[github-actions]

We found the following entry in the FAQ which you may find helpful:

• How do I pass arguments to an app?

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

This project is developed and maintained by Will McGugan. Consider sponsoring Will's work on this project (and others).

This is an automated reply, generated by FAQtory

[willmcgugan]

Not much you can do after a hard crash. You could run the dangerous code in a subprocesses which would provide some isolation. Otherwise the only option is to type reset.