Occasional crash when running project(?)

[gsteinLTU]

I'm not sure what exactly caused this, I ran a program with just some string operations and pen drawing, when I added a print statement and then tried to run it, it crashed (and unfortunately took the code with it):

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/gordon/.pyenv/versions/3.12.10/lib/python3.12/site-packages/netsblox/__main__.py", line 2, in <module>
    main()
  File "/Users/gordon/.pyenv/versions/3.12.10/lib/python3.12/site-packages/netsblox/app.py", line 2881, in main
    root.mainloop()
  File "/Users/gordon/.pyenv/versions/3.12.10/lib/python3.12/tkinter/__init__.py", line 1505, in mainloop
    self.tk.mainloop(n)
  File "/Users/gordon/.pyenv/versions/3.12.10/lib/python3.12/site-packages/netsblox/app.py", line 1361, in _proxy
    raise e
  File "/Users/gordon/.pyenv/versions/3.12.10/lib/python3.12/site-packages/netsblox/app.py", line 1354, in _proxy
    result = self.tk.call(cmd)
             ^^^^^^^^^^^^^^^^^
_tkinter.TclError: bad text index ""

It happened multiple times now, but I don't think it's dependent on the code. I recreated the code from the initial crash and it didn't crash when run, but a few modifications later running the same crash occurred.

[dragazo]

Hmm, looks like that's in the IDE code too. And it only happens when running the code? The runner is a separate process that just communicates over a pipe, but the main app does poll the pipe contents and throw it into the program output panel, so I suppose something can go wrong in there. Do you happen to have a version of the project before the crash I can use to try to recreate it?

[gsteinLTU]

Yes, it only happens when running.

Here's the project (well, the recreated one since the crash lost the original code), but it doesn't cause it. Adding the print statement in the onstart seemed to be related, but I'm not sure if it actually is.
tree1.json

If we can't track it down, maybe we just check that cmd is valid.