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
bpasero
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Apr 28, 2016
@v-pavanp 'smart step' makes only sense if your project is using source maps and those sourcemaps cover most of the source code of the project. It seems your project is a plain JavaScript project without a single source map. Why would you use 'smart step' in this case? Just to be slower?
Mixing works fine as long as the JavaScript you are stepping through is reasonable small (for instance because it is just glue code generated by a transpiler).
If you have lots of JavaScript that does not map to some source language, using this option makes you slow because node debug has to single-step through the JavaScript.
So the slowness you are seeing is expected and not a bug.
Testing: #4954
Steps to Reproduce:
Note: I tried with all the possible combination of smartstep and sourcemap and observed this behavior when both the properties set to true.
Actual: Debugging is super slow and taking long time to render page.
Expected: Debugging should not be slow down when user enable smartstep.
The text was updated successfully, but these errors were encountered: