Could attach test project? See http://youtrack.jetbrains.com/issue/WEB-6581

One possible cause of this is the JetBrains Chrome Extension,

I didn't have it installed before I upgraded to WebStorm 6, now, even after I've gone back to using WebStorm 5, my debugging is very slow, I've even uninstalled the Chrome Extension and I have the same problem.

Please Help!

-Matt

How long does it take for debug mode from the command line (without WebStorm) to start for you?

For example, in your project directory, try

node debug app.js

One note:

if I start on the command line with: node --debug-brk=56986 server.js

and then open my browser to:

http://127.0.0.1:56986

then the debugger process wakes up or stops hanging and I see my console messages.

Perhaps there is something similar going on when I debug through webstorm where it is waiting for the connection from the chrome extension?

-Matt

I was able to get the breakpoints working in my small (mocha test) configuration.   I think the key was by upgrading the nodejs plugin within webstorm.

After that was working, I noticed that in my larger project (with express, etc...) if I startup with the option of "break on all exceptions" I see it breaks immediately.  I tried this because I noticed this bug:

http://youtrack.jetbrains.com/issue/WEB-1917

mentions that breaking on all exceptions shows breakpoints.

As I step through after "Breaking on all exceptions" it hits the fs.js file under frames in the debugger tab (as shown in the screenshot) and the path shows it hitting this exception for just about every node_module.

This could explain why it's taking forever to startup the debugging if it's hitting exceptions for whatever reason in every one of my node modules.

Hope this helps get the the bottom of the issue.  I'd rather not have to rebuild my whole machine to get the debugging working correctly again in WebStorm.

thanks,

-Matt

Any updates on this issue?

My coworker had tested his debugger again and notified me that it was broken (super slow) for him as well.  I suspect it may be caused or made worse by some recent node_module put into our repository, I tried removing some of the more recently added modules though and it didn't help, so it's still a mystery to me.

thanks,

-Matt