You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> c:; cd 'c:\path\to\folder'; &'c:\Users\user\.vscode\extensions\vscjava.vscode-java-debug-0.35.0\scripts\launcher.bat''C:\jdk-16.0.2\bin\java.exe''-agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:53340''-Xmx24G''-ea''-XX:+ShowCodeDetailsInExceptionMessages''-Dfile.encoding=UTF-8''@C:\Users\user\AppData\Local\Temp\cp_c5uy9eqnavixxyehhdl84kqui.argfile''my.run.class'
With a running debugging session, this is shown on the variables pane of the debugger side bar. Also, no values of variables are shown while hovering over them.
Expected Result
Showing locals and providing variable value hovers should still work even if large objects are created.
Additional Informations
If I'm allowed to speculate here: The log suggests that something is copied which might not be wise with very large objects. Running the class without debugger works totally fine.
Thank you for your work for bringing Java support to VS Code.
The text was updated successfully, but these errors were encountered:
From the logs, the exception appears that when the Variables view tries to evaluate toString() value of a large object. I also observed that when the local variable contains a large HashMap object, it takes a long time to display the Variables view.
Current workaround is to disable "toString()" view.
The Java debugger fails to show locals after a large object is created in the current scope.
Environment
Steps To Reproduce
Launch Command
Log
Current Result
With a running debugging session, this is shown on the variables pane of the debugger side bar. Also, no values of variables are shown while hovering over them.
Expected Result
Showing locals and providing variable value hovers should still work even if large objects are created.
Additional Informations
If I'm allowed to speculate here: The log suggests that something is copied which might not be wise with very large objects. Running the class without debugger works totally fine.
Thank you for your work for bringing Java support to VS Code.
The text was updated successfully, but these errors were encountered: