Skip to content

[feature request] lazy load object variables while attach debug #311

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

Open
nghduc97 opened this issue Jun 17, 2018 · 2 comments
Open

[feature request] lazy load object variables while attach debug #311

nghduc97 opened this issue Jun 17, 2018 · 2 comments
Assignees
Labels
performance variables voting Please vote on the issue, so that we will take priority to this issue.

Comments

@nghduc97
Copy link

In attach debug, if there are a lot of local variables containing array of objects, the extension fetch a deep copy back to the editor making each step very slow. IntelliJ run fast by only showing the variable's name and type and only fetch the content when I unfold it in watch panel. I would like to have this on the extension.

Environment
  • Operating System: Arch
  • JDK version: 9.0.4
  • Visual Studio Code version: 1.24.1
  • Java extension version: 0.26.0
  • Java Debugger extension version: 0.9.0
@nghduc97 nghduc97 changed the title [feature request] lazy load object variables with attach debug [feature request] lazy load object variables while attach debug Jun 17, 2018
@yaohaizh
Copy link
Contributor

@testforstephen Could you help investigate this issue on the debug protocol?

@andxu
Copy link
Contributor

andxu commented Jun 19, 2018

That is possibly caused by we hint vscode a cheap local scope
https://github.com/Microsoft/java-debug/blob/master/com.microsoft.java.debug.core/src/main/java/com/microsoft/java/debug/core/adapter/handler/ScopesRequestHandler.java#L50

We can hint vscode expensive fetching on attach mode.

@andxu andxu added the voting Please vote on the issue, so that we will take priority to this issue. label Jun 20, 2018
@andxu andxu added this to the 0.12.0 milestone Aug 7, 2018
@akaroml akaroml mentioned this issue Aug 8, 2018
14 tasks
@andxu andxu removed this from the 0.12.0 milestone Aug 30, 2018
@andxu andxu removed the priority/p2 label Nov 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance variables voting Please vote on the issue, so that we will take priority to this issue.
Projects
None yet
Development

No branches or pull requests

4 participants