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.
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.