3 ms·

One thing that always surprises me with Chrome (and other browsers) is how easy it is to get a browser tab to freeze by running an infinite loop in JS. This hap

One thing that always surprises me with Chrome (and other browsers) is how easy it is to get a browser tab to freeze by running an infinite loop in JS. This happens to me from time to time due to programming errors and I usually have to close the entire browser to fix it, as the tab will neither close nor will I be able to access the developer console to turn the script off. That probably means the script runs in the same thread as the render/UI code for a given tab? Anyway I found this quite annoying and I wondered why the browser behaves like this (I’m sure there’s a good technical reason as other people must have encountered the same problem so if this was easily fixable someone would’ve probably already fixed it).

georgemcbay 8y ago
A similar thing that surprises me is how malicious ad networks are still able to effectively get your Chrome tabs into states where you can't easily close them without killing the entire chrome task. While I'm sure there is a lot of complexity there that I'm not considering to avoid messing with legitimate usages of tab closing event handling by real apps, it would be nice if there were some kind of like alternate tab close input (eg. hold ALT or SHIFT, or both while clicking the tab 'X') where the user is signalling the intent that "yes, I absolutely want to close this tab, no matter what, kill it with extreme prejudice". If such a thing exists, which it might, someone please correct me by telling me what it is.
palimpsests 8y ago
You can kill this tab without closing the browser by using 'end process' in Chrome's Task Manager (available under the Window menu).
- kartickv 8y ago
  But that's unintuitive. Why can't you click the X button on the tab to close it? That's browser UI, not web page UI, so it should never be unresponsive.
  - palimpsests 8y ago
    I was responding to the parent comment with a way to kill the tab without quitting the browser, that's all. I didn't make this feature; I don't have the answer to your question. It was intuitive enough for me to find it on my own without reading any documentation. So, shrug.
    - kartickv 8y ago
      I wasn't criticising you, just asking the more general question here of why clicking the close button doesn't work reliably.

georgemcbay 8y ago

A similar thing that surprises me is how malicious ad networks are still able to effectively get your Chrome tabs into states where you can't easily close them without killing the entire chrome task. While I'm sure there is a lot of complexity there that I'm not considering to avoid messing with legitimate usages of tab closing event handling by real apps, it would be nice if there were some kind of like alternate tab close input (eg. hold ALT or SHIFT, or both while clicking the tab 'X') where the user is signalling the intent that "yes, I absolutely want to close this tab, no matter what, kill it with extreme prejudice". If such a thing exists, which it might, someone please correct me by telling me what it is.

palimpsests 8y ago

You can kill this tab without closing the browser by using 'end process' in Chrome's Task Manager (available under the Window menu).

kartickv 8y ago
But that's unintuitive. Why can't you click the X button on the tab to close it? That's browser UI, not web page UI, so it should never be unresponsive.
- palimpsests 8y ago
  I was responding to the parent comment with a way to kill the tab without quitting the browser, that's all. I didn't make this feature; I don't have the answer to your question. It was intuitive enough for me to find it on my own without reading any documentation. So, shrug.
  - kartickv 8y ago
    I wasn't criticising you, just asking the more general question here of why clicking the close button doesn't work reliably.