Webstorm debugging: startup time went from 15s to 50s

Hi, I'm trying to figure out why debugging my node.js app is taking so much longer in one environment as compared another:

Environment 1 (normal):
Time to launch app when Running: 6s
Time to launch app when Debugging (0 breakpoints): 9s
Time to launch app when Debugging (2 breakpoints, none hit): 10s
Time to launch app when Debugging (10 breakpoints, none hit): 11s

Environment 2 (slow):
Time to launch app when Running: 6s
Time to launch app when Debugging (0 breakpoints): 9s
Time to launch app when Debugging (2 breakpoints, none hit): 23s
Time to launch app when Debugging (10 breakpoints, none hit): 34s

My environments consist of the same source code, but mapped to different folders on the same local disk.

I'm on Webstorm 2018.2.5. I didn't see any debugging options that could vary between the two. Am I missing something pls?

9 comments
Comment actions Permalink

What Node.js version do you use, is it the same in both environments? Also, do you have exception breakpoints enabled (Run | View Breakpoints..., JavaScript Exception Breakpoints?

BTW, Webstorm version you are using is quite old, does upgrading make the debugging faster?

0
Comment actions Permalink

Hi Elena, thanks for writing.

I'm running Node 8.16.0 on both. 

If there are no known issues with my current configuration I'll try upgrading to 2018.3, which is the highest that I'm licensed for. THanks!

0
Comment actions Permalink

I'm not aware of any similar issues:(

0
Comment actions Permalink

Webstorm 2019.2 doesn't seem to help:

Time to launch app when Running: <6s
Time to launch app when Debugging (0 breakpoints): 9s
Time to launch app when Debugging (2 breakpoints, none hit): 27s
Time to launch app when Debugging (10 breakpoints, none hit): 45s

From the looks of it, 2019.2 made things slower when breakpoints were active! :D

BTW I never had Exception Breakpoints active.

0
Comment actions Permalink

Please enable js.debugger.wip.log in Registry (Help | Find action, type Registry... to locate it) by setting it to path to some temporary file like C:/tmp/wip.json, recreate the issue and provide this log along with your log folder zipped (Help > Compress Logs and Show in ...). Note that the debug log will be re-written on each debugger start, so it's important to copy the log right after reproducing the issue

0
Comment actions Permalink

Hi Elena, I grabbed a set of before/after logs for my app startup. Right off the bat I'm noticing that the slow version has a lot of these pairs of events:

{"timestamp": "11.46.37,007", "IN": {"method":"Debugger.paused",...}}
{"timestamp": "11.46.37,008", "OUT": {"method":"Debugger.resume","id":40}},

The Slow version has 560 of these pairs while the fast version only has 2 of these pairs.
I know I'm not pausing the debugger in either of those runs. Do you know what might be causing these? I'm certain this difference is what's making my 'slow' run as slow as it is.

0
Comment actions Permalink

Hi Jeffery,

Could you please share any whole line from that log, starting from  {"timestamp": "...", "IN": {"method":"Debugger.paused"..? Somewhere from the middle.

0
Comment actions Permalink

Yes, thank you, but sadly this is now what I expected to see. How many breakpoints do you have? Can you please check if setting js.debugger.async.call.stack.depth to 0 in Help | Find Action... | Registry... improves the situation? If not, we'll need the complete debugger log to investigate it further. You may send it privately via opening a support ticket from https://intellij-support.jetbrains.com/.

0

Please sign in to leave a comment.