5 ms·
The most recent version of chrome has made having a breakpoint a painful affair. * The browser becomes completely unresponsive, each time you hit a breakpoint
by syspec 7y ago
The most recent version of chrome has made having a breakpoint a painful affair.
* The browser becomes completely unresponsive, each time you hit a breakpoint for 3-5 seconds.
* It also takes chrome much longer to show you the source maps for a page
* If you refresh while on a breakpoint it will remain unresponsive for nearly 10 seconds.
Is this related to these new changes? Is there a way to revert the trade off?
- JMTQp8lwXL 7y ago> * If you refresh while on a breakpoint it will remain unresponsive for nearly 10 seconds. Glad to hear I'm not alone in experiencing this. For a period, I thought I had written bad code that caused Chrome to stumble. Guess it's just Chrome.
- natorion 7y agoCan you please file a bug report on crbug.com?
- mehrdadn 7y agoHow are Chrome devs themselves not experiencing this? I've experienced it too...
- JMTQp8lwXL 7y agoIt seems like such a common action, I'm surprised a non-Chromium developer would have to report it. I considered reporting it, but too much friction. I need to use a Google Account to report a bug? Why? Eh.
- djmips 7y agoIt's easy to conceptualize a configuration or use case that's common to the people reporting a bug that's not being used by the developers or in their QA process. It's not uncommon.
- lacampbell 7y agoThanks for sharing this. Same problem, I just assumed it was just my shit tier laptop!
- jlu 7y agoFor anyone who's affected by this, I just filed a bug via crbug.com, fingers crossed for it to be fixed ASAP. In the mean time, one work around is not to hit refresh, instead hit F8 and let it exit the breakpoint normally.