JavaScript Debugger Seems to Lose Connection
I'm experiencing issues when debugging JavaScript served by Webpack in Chrome. It used to work just fine.
Console is listing the first log entry, any following log entries are only visible in Chrome, not in IntelliJ IDEA. Issuing a console.log('test') will return Failed to send.
Consequently also breakpoints are not entered any more.
Sometimes, but not always, I'm getting a warning "Waiting for connection to localhost:54253."
I can fix the issue by restarting IntelliJ and Chrome, but it is reproduced by reloading once in Chrome.
Could this be a firewall configuration that blocks communication to localhost:54253? How could I check?
IntelliJ IDEA is 2019.3.1
Please sign in to leave a comment.
Firewall can indeed be the issue...
Are there any specific steps that lead to it? please enable
js.debugger.wip.login Registry ( Help | Find action, typeRegistry...) by setting it to path to some temporary file like/tmp/wip.json, repeat the issue and provide this log along with your idea.log (https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files). Note that the debug log will be re-written on each debugger start, so it's important to copy the log right after reproducing the problemIt's really weird:
First Console is showing all log entries and updating synchronously with Chrome.
Then there's a flush of log entries, and only the very first log error is visible. Console is not updated any more, and no console.log() can be issued.
Chrome is continuing to load the application, and producing log entries.
It's hard to figure out which step in loading the application cuts communication, since the Console is cleared.
Btw, when re-running debug, the same Chrome window is used, the tab gets updated.
Here are my logs: https://send.firefox.com/download/c04c0ba961e4e058/#hvOKc9v6oZgkVvmvN_B6SQ
Thanks very much!
Thanks!
The logs show that the debugger breaks when attempting to load a huge file through a websocket:
io.netty.handler.codec.http.websocketx.CorruptedWebSocketFrameException: Max frame length of 104857600 has been exceeded
Splitting the generated bundles in smaller chunks would likely help...