New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash, lost work in progress #1268
Comments
@brodney we'd love to help, but really need more details. |
Pardon my initial frustration, I lost a good bit of work. Redid it, even better now. The online editor in Safari locked up and appears to be locking up pretty frequently now. Activity Monitor reported several threads each around 20% utilization. Additionally it gets stuck (pinwheel) when I make changes to the file and it attempts to parse to display the documentation. When that happens it won't update the error message even when fixed or change. |
Thanks for the details. We recently released a new version of the editor, but that's not available online yet (soon). Can you try running the editor from a clone of this repo? You only need to open the index.html file at the root, no build required. |
Sure which branch? |
Just master. |
Couple bugs for you:
No crash or performance issues I'm seeing though 👍 . The error reporting seems much much faster to show up and disappear, and hasn't hung as I tried adding a new object type and using it here or there. I'll use this for now and report back if anything happens again. |
Thanks for the feedback, @brodney. You mentioned you use Safari - which version of Safari? Would you mind testing the file opening with a different browser too? |
10.0.3 on Sierra. No issue opening on chrome. |
Thanks for your patience and checking things, @brodney. I really appreciate the help. If you don't mind, could you open a separate ticket for one of the two issues you mentioned here. It's easier to handle isolated issues, and I normally prefer users to open the tickets so they get notified about the progress properly. |
The bugs mentioned upthread appear to have been fixed a while ago, so I'm going to close this ticket. Thanks for the report, @brodney! Please ping if you're still experiencing any of these issues. |
Thanks.
The text was updated successfully, but these errors were encountered: