JavaScript debugger slow in 2016.3

JavaScript debugger issues in 2016.3. My javascirpt debugger appears to not work but actually it's fully functional but very (very!) slow. Even clicking to add a breakpoint in the editor takes about 30 seconds to appear.

Is anyone else having this issue? 

IntelliJ IDEA 2016.3
Build #IU-163.7743.44, built on November 17, 2016
JRE: 1.8.0_112-release-408-b2 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

On Mac : 10.12.1



is it about client-side debugging, or about Node.js? In the latter case, what Node.js version is used?


It's client-side, using the IntelliJ "JavaScript Debug" configuration, Chrome extension "JetBrains IDE Support 2.0.9" in Chrome Version 54.0.2840.98 (64-bit)




hmm... does the problem only occur when debugging? Also, when does it run slow - on debug session start, on updating variables view once breakpoint is hit, or?


IDE seems fine normally, just starting the JavaScript debugger causes the issue. It seems to me that the communication between the browser plugin and IntelliJ is potentially the issue, at least that's what it looks like. The issue starts when you start to debug, and IDE goes back to normal after closing the browser or terminating the debug session in the normal way. 

I installed IntelliJ 15 and had the same issue, so must be my local environment it some way. 

Any tips for debugging? 



I received a LiveReload update this morning and it's running much better now. It's still slow for some actions e.g. adding and removing breakpoints, but stepping through code and inspecting local variables etc.. is working much better.  


Haven't been using the js debugger due to the slowness, tried it again this week after 2017.1 and it's really slow. Takes a good few minutes to launch the page and then stepping through code is very slow, so much so that it's unusable. 

It's hard to take a CPU profile as interacting with IntelliJ is virtually impossible after launching the debugger. If I wait until it gets past the initial loading I can take a memory snapshot. Creating a new Hello Would project the debugger works fine. So I guess it's something to do with my current project, though it's not at all big, just a small Backbone app.


>It's hard to take a CPU profile as interacting with IntelliJ is virtually impossible after launching the debugger

start the profiler, then launch the debugger and, once the page is loaded, stop it. Then stop the profiler.

Thread dumps ( taken while page is loading might be also helpful


Please sign in to leave a comment.