-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Custom Hover in REPL freezes the UI #210518
Comments
Guessing this is a consequence of using the more convenient but less performance-conscious |
adding |
+@aiday-mar was this change part of the hover enriching work you did? I think when using hovers extensively like this you need to move off |
Hi @Tyriar probably not, the hover enriching work is not merged yet. I have done some refactoring on the content hover however so if there is a link somewhere to the content hover code it could be caused by that. |
This might be the culprit if the problem is hover related: #209058 @connor4312 Do you think this is actually hover related? It looks like there are a lot of |
Hover does seem like the majority but |
I assume this happens when a breakpoint gets hit, do you recall where you placed that breakpoint when you got that profile @rebornix? |
@connor4312 I used breakpoints briefly while debugging, but I can' recall if they were still enabled when I did the profile. |
Do you know in general what you were doing so I can try to reproduce? I don't think I've hit this before in my debugging. The only slowness I get in the copilot repo is when dealing with source map renames making the initial 'variables' view slow to load (TBD whether there's much I can to do speed that up) but that's not renderer-blocking. |
Coming back a bit late. I don't really have a good reproduce. |
Fixed in microsoft/vscode-js-debug#2000 |
Does this issue occur when all extensions are disabled?: Yes/No
I ran into this pretty often while debugging extensions
and digging into the call stack, it's coming from custom hover handler for REPL
The text was updated successfully, but these errors were encountered: