How to debug unresponsive page in Google Chrome?
google-chrome, javascript
Solution
I know this is an old question but I had this problem as well, and my best recommendation to you is the following:
Close Chrome completely and then add " --enable-logging" to your chrome shortcut to start it with that flag, you can even add " --enable-logging --v=1" to enable verbose logging.
I know with me, inserting a breakpoint wasn't an option because it was in a new tab that crashed before I could even get the console up. However, by enabling logging, the console gets written to a file in your chrome data directory ("C:\Users\username\AppData\Local\Google\Chrome\User Data")
I hope this helps somebody someday like it did me! :D
Problem
I've got a fairly complex javascript application (it uses no external frameworks) that users are currently testing (a couple thousand lines). I've been getting reports that users are getting the popup in Google Chrome saying: The following page(s) have become unresponsive. You can wait for them to become responsive or kill them. They report that the only way to keep using the app is to open a new Chrome window, but that the messages comes back up every few minutes, and only happens when they try to go to a new page. They specifically said that they click to go to a new page, and the current page never changes, they just see the spinning loading icon for a minute until the popup comes sup. The odd thing is that I've tested extensively on the exact version of Chrome (18) that these users are having issues with, and I've seen no problems. I'm sort of stumped and don't know where to look now since I've been unable to duplicate it, any ideas on where to look next to at least try and figure out what could even be causing that error?