Yeah the debugger certainly still leaves some things to be desired. When using a fairly sizeable react project, I set a XHR breakpoint, it was triggered, then the whole tab became unresponsive (dev tools included)
This happens to me a lot in the Chrome developer tools as well. Especially with hot reloading, so would love any advice to help with it. Chrome is the only application I ever have to force quit.
Happens to me in Chrome too, specifically when I reload a page that's stopped at a breakpoint. Instead of force quitting the whole application, check out Window -> Task manager. There you can force quit just a single, specific tab without closing the whole application.
The chrome task manager (hotkey Shift+Esc) is good for killing tabs
For large pages where source changes cause problems I will sometimes put logic inside conditional breakpoints. It's not great for huge changes (though you technically can put a lot of code in there) but for small things like quickly sanitizing null inputs it works fine.
