You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening ZeroBrane Studio, it tries to recover a very long (10,000 line) minified lua file and seems to hang forever (hours). Every time I open the studio, it will hang before I can close the problematic file as it tries to open the 'remembered open files'.
I assume there is no way to fix this hanging-loop other than uninstalling and reinstalling ZBS - I propose there be added a timeout for trying to open auto-recovered files of something like 60 seconds, so that this doesn't happen.
The text was updated successfully, but these errors were encountered:
@zet-dota, thank you for the report. You can remove the session configuration file (see this section in the documentation to find its location, as it's system-dependent), which should fix this issue.
If you want me to take a look to see how it can be addressed, feel free to email me the configuration file before deletion (to the email address in my github profile).
If you don't want to delete the settings (as it will wipe out your file list, project list and other settings), then open the file and find [session] section and remove it along with recovery record in it.
I suspect it may not be related to the recovery record itself, but to the handling of that 10k minified file, which likely doesn't have any new lines. That's why I thought it may be useful to look at what's going on there.
When opening ZeroBrane Studio, it tries to recover a very long (10,000 line) minified lua file and seems to hang forever (hours). Every time I open the studio, it will hang before I can close the problematic file as it tries to open the 'remembered open files'.
I assume there is no way to fix this hanging-loop other than uninstalling and reinstalling ZBS - I propose there be added a timeout for trying to open auto-recovered files of something like 60 seconds, so that this doesn't happen.
The text was updated successfully, but these errors were encountered: