WebStorm debugger is extremely slow to start w/ Node.js 5.0.0

[unbornchikken]

Here we go again. Looks like our friend is back again with Node.js 5.0.0. Confirmed w/ WebStorm 11.0.1 + Node.js 5.0.0. Reported there: https://youtrack.jetbrains.com/issue/WEB-19117

@develar I'm opening that there too, it might caused by a new v8 stuff.

[hilkeheremans]

+1, confirmed here as well.

[bnoordhuis]

Is there reason to believe it's a node.js issue? IIRC, last time it was weak interaction between V8 and WebStorm.

[develar]

I don't experience any problem during fixing https://youtrack.jetbrains.com/issue/WEB-18853 I will check again ASAP, but, may be, it is already fixed in the not yet published WebStorm 11.0.2.

[hashseed]

Anyone able to try this patch to see whether it fixes anything? https://codereview.chromium.org/1454673002/

[unbornchikken]

@bnoordhuis You're right, but people will experience this issue when use WebStorm to debug their Node.js 5.0.0 applications. So, I believe that it's better to track there as well, to prevent it arise in this list over and over again.

[HowlingEverett]

@develar I'm running the Webstorm 11.0.2 EAP, which includes WEB-18853. It fixes the debugger not running at all, but I still have a 30s+ wait for the debugger to launch and connect when running Node 5.0.

[HowlingEverett]

This appears to be a debugger issue, not Webstorm specific. I get a similar delayed startup time when loading node-inspector with the same project.

For context, I'm also transpiling using require("babel-core/register), but disabling the babel compiler doesn't seem to have any effect, it's still slow.

[ofrobots]

It would be nice if there was a reduced test case that could be generated from these debugger startup paths. That would be useful in verifying issues like this.

[HowlingEverett]

I'll try to put something together. I'm not sure how reduced it can be since the slowness of the startup time seems to be dependent on the number of modules loaded in the application code e.g. If I create a trivial application the debugger session starts instantly, but as you start loading modules the load time grows ... Something worse than linearly...

Cheers,
Justin

On 2 Dec 2015, at 3:58 PM, Ali Ijaz Sheikh notifications@github.com wrote:

It would be nice if there was a reduced test case that could be generated from these debugger startup paths. That would be useful in verifying issues like this.

—
Reply to this email directly or view it on GitHub.

[develar]

Problem for me — that I don't have complex NodeJS app to feel the difference. Can somebody send me (attach to https://youtrack.jetbrains.com/issue/WEB-19117 and set visibility "jetbrains-team") test project?

Is startup slow in case of sample express project ("Node.js Express App" template)?

[develar]

Reproduced — v5.1 is dramatically slow compare to v4.2.2.

[hilkeheremans]

Please note that someone is reporting this is also occurring with node-inspector.

nodejs/node-v0.x-archive#9125

[develar]

@yangguo-chromium I applied https://codereview.chromium.org/1454673002/ patch to nodejs 5.x sources —doesn't fix the issue.