-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Output window gets stuck constantly appending to queue #1509
Comments
I think I encountered that the other day. It was too strange for me to make any sense of that single time. |
@stefan-toubia Can you reproduce this consistently? If so, can you provide a repro case? I haven't experienced this, that I know of, but a repro case would help with testing the PR. |
@bpringe I have not been able to reproduce this consistently, though it's at least a daily occurrence for me. The only reason I was able to identify the cause was by launching calva with the debugger turned on and getting lucky with break points. I haven't seen a specific pattern. Sometimes it gets into a bad state nearly immediately after starting vscode, before ever starting a repl. Most of the time though it's after a few hours of working with a repl and then trying to restart the repl with jack-in. |
Seems this wasn't linked properly to be closed when the changes were merged to |
I've identified a long running issue where the output window gets into a bad state and no longer updates with new output. What I found is that the current logic which uses an
isUpdating
flag encounters some edge condition that causesisUpdating
to never get cleared, causing the queue to grow indefinitely and require a vscode restart.The text was updated successfully, but these errors were encountered: