-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Debugging with smartstep is super slow. #5916
Comments
@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? |
No, but how about mixed TypeScript and JavaScript projects. |
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: