> Isn't the correct behavior when an application goes past resource limits to crash the app? Maybe, or maybe it would be better to exponentially decrease CPU t

> Isn't the correct behavior when an application goes past resource limits to crash the app? Maybe, or maybe it would be better to exponentially decrease CPU time awarded to a tab over time. And ask the user to confirm that this tab should be allowed to do CPU / memory intensive computations, and otherwise reduce the frame rate, number of ticks, or crash early. Maybe, big memory allocations and CPU intensive stuff should only be allowed on background workers. And even then, we should still reduce resource allocations to save battery, etc. and allow users to award more resources. > He means crash the single web page doing the loop... how would you fix this? It used to be that you could bring my entire system to halt by allocating too much memory in the browser (mostly chrome). Mostly due to swapping and just plain bad system configuration I suspect :)