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
Now if I install 0.8.1-beta.12 or 0.9.1, debugging is slightly to significantly slower depending on the amount of variables that are getting collected by the debugger. Setting showGlobalVariables to false (as mentioned here: #2133 (comment)) doesn't really seem to do anything for me (there might be a slight improvement but there is noticeable lag here that is not present in the beta version 0.8.1-beta.7 I mentioned above). Regardless of whether or not showGlobalVariables is set to false, global still appears in the frame:
I'm guessing that there is still some other processing being done here in the latest versions that wasn't being done in versions where the debugger works much more fluidly. Is there a way to just completely disable global variables? Is this even expected when showGlobalVariables is set to true? Global variables aren't really recommended in general by the go community anyways so an option to disable them completely in favor of higher performance would be appreciated.
Steps to Reproduce:
Run debug session with above config
Debugging is slow, global variables still appear in the variables pane.
If I'm using the extension version

0.8.1-beta.7debugging is very fast and onlylocalappears in the variable window:config:
Now if I install
0.8.1-beta.12or0.9.1, debugging is slightly to significantly slower depending on the amount of variables that are getting collected by the debugger. SettingshowGlobalVariablesto false (as mentioned here: #2133 (comment)) doesn't really seem to do anything for me (there might be a slight improvement but there is noticeable lag here that is not present in the beta version0.8.1-beta.7I mentioned above). Regardless of whether or notshowGlobalVariablesis set tofalse,globalstill appears in the frame:I'm guessing that there is still some other processing being done here in the latest versions that wasn't being done in versions where the debugger works much more fluidly. Is there a way to just completely disable global variables? Is this even expected when
showGlobalVariablesis set totrue? Global variables aren't really recommended in general by the go community anyways so an option to disable them completely in favor of higher performance would be appreciated.Steps to Reproduce: