-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Step over and Step in are quite slow #127720
Comments
I can confirm that step over is much slower than it was earlier |
I see it too, maybe its related to the timer and spinner fix? |
Hey @isidorn, I have this code to update some notebook metadata based on the current debug state, but it slows things down by generating too many callstack requests, and I don't know how to do this the right way vscode/src/vs/workbench/contrib/notebook/browser/contrib/breakpoints/notebookBreakpoints.ts Line 115 in 0a3b4bd
I think one problem is that we might call And I have to call fetch, because otherwise the callstack is empty when the (There are 4 threads) So it's not clear to me how to do this efficiently. |
@roblourens so you just want to be called every time the call stack changes, but that the stackFrames are all fetched correct? We might need to introduce a new event You should not need to call |
I don't think I want to ask for all stackframes every time, because currently you don't actually request all stackframes unless the callstack is visible and the user clicks "Load more", right? And I don't want to cause more load. I think I just want to be notified when the top 20 frames are available. |
Yeah, we only request all the stack frames once the user clicks on the "Load more". Alternatively maybe you could listen on |
I just disabled the whole thing for now. To verify, stepping in a notebook cell should not feel extremely slow. |
Still much slower than say a typescript file, but faster than before. |
Testing #127362
The text was updated successfully, but these errors were encountered: