Increase LogLevel for Webstorm to analyze strange debugging issue

Hello everyone,

got a small problem with WebStorm and wanted to see, if anyone had a similar problem.

I am using Webstorm 9 (Build 139.1112) with Node.js 0.8.14 on a Linux Mint system using Oracle JDK 1.8.0_25.

For a long time I could start my Node.js project in debug mode and everything went smoothly. Yesterday out of the blue the debugger started to hang, i.e. webstorm java and nodejs process cpu usage dropped to nearly zero, and after about 7 to 8 minutes later the process woke up again and kept on with delivering pages. Now the strange thing is, if I do not use the debug mode, everything performs absolutely normal. Even worse is, that a single breakpoint inside a JavaScript file prevents the 8 minute timeout from happening.

So the only way to reproduce this problem is by using the WebStorm debugger and not having a single breakpoint, which makes debugging this problem quite a task.

Another strange behaviour is, that this 8 minute hiatus does not occur all the time. Sometimes I can start the debugger a couple times and everything is fine, and suddenly it stops working again. Once it does that I can not make this behaviour go away, without restarting the PC. Neither a WebStorm cache clean helped, nor removing the project settings or cloning the repository and begining from scratch. I already checked, if there were any dangling file handles or open ports left behind by a crashed debugger, but nothing. Same when I check the open handles of WebStorm or the Node.js debugger process. There is nothing unusual.

Ok, so much for the problem description. My question now is wether there is a chance to increase the loglevel of WebStorm to DEBUG instead of INFO. I want to see what is happening and where the process stops to further investigate this, otherwise I am at a loss.

Maybe someone had a similar issue, a colleague of mine uses IntelliJ with the same repository and does not have this problem, so it very likely is something with my system.

If more information is needed, just ask and I will provide it.

Greetings

Ben

2 comments
Comment actions Permalink

You can enable debug logging for debugger.

<category name="#org.jetbrains.io.jsonRpc.JsonRpcServer">
<priority value="DEBUG"/>
</category>
<category name="#org.jetbrains.v8.EventMap">
<priority value="DEBUG"/>
</category>
<category name="#org.jetbrains.v8.AfterCompileProcessor">
<priority value="DEBUG"/>
</category>
<category name="#org.jetbrains.v8.connection.V8MessageDecoder">
<priority value="DEBUG"/>
</category>
<category name="#org.jetbrains.rpc.MessageManager">
<priority value="DEBUG"/>
</category>
<category name="#org.jetbrains.io.ChannelExceptionHandler">
<priority value="DEBUG"/>
</category>

Then restart WebStorm and recreate the problem - idea.log will contain debug logging

0
Comment actions Permalink

Thanks for your information Elena. That did produce output, but I still don't understand the issue. Somehow it hangs in a deeply nested node.js module, throws an error, keeps on with the execution but yet it does not use any cpu time ... this is very strange. Even stranger is the fact, that it started to happen yesterday out of the blue, without me changing anything on the system or in the repository.

Anyway, for now I have a workaround. Will investigate the issue some more when time permits.

Greetings

Ben

0

Please sign in to leave a comment.