This might exist on older versions.
I’ve encountered an issue where the gcode parsing would look like it locked up while analyzing after loading a new .ngc file. I could abort, but even loading other known good files would not work correctly. I had to restart between each test debugging the issue.
I was able to track it down to this line:
T4(#45634-K 30° V GROOVE 1/4 DIAMETER 1/4 SHANK)
The degree symbol was causing the issue.
Could you add something so it will ignore invalid characters inside a comment?
And can you look into adding a “busy” indicator? Examples are searching for networks, connecting to network, update from file, etc. These take the first button input but give no indication if it is doing something or finished with no response. Clicking somewhere else does nothing until the initial action is complete and then tries to do the second click.