It is a known issue and it has not been adressed by anyone yet.
The underlining compiler (inklecate in its own subprocess) will be shutdown and relaunch everytime you type something in the ink source (left panel)
Just writing a random “~” in the ink source will result in a parse error and effectively stops it right there, giving you a chance to rewind everything and find the bug in your code.
If you’re a tech savvy linux user you may be able to find the abovementioned inklecate process and kill it