|
|
|
|
|
|
by rty32
677 days ago
|
|
|
I do think such mechanisms exist in various places. CPU intensive browser pages (e.g. running an infinite loop in JavaScript) would leave the page unresponsive, but the browser and the OS in general is still fine. You can easily close the page causing trouble. Well, at least in desktop Chrome and Firefox. I definitely haven't seen one page slowing the entire browser since the IE days. On the other hand, if a (general) Android app is not responsive, there is also a dialog inviting you to kill it ("[app name] isn't responding - Close app"). But this one is different. I don't know the underlying mechanisms for the browser and the OS, but it almost feels like a bug. |
|
|