Each tab should get a certain number of credits to use CPU cycles, like a ticking time bomb when it runs out it should detonate and self-close (or just stops up

Each tab should get a certain number of credits to use CPU cycles, like a ticking time bomb when it runs out it should detonate and self-close (or just stops updating.) Perhaps then the browser in the next request to the same URL sends a header notifying the server that its page ran out of credit in x amount of time so the author can optimize it. Another idea is to look at other Chrome users activity pattern in regards to how often a given URL is kept hidden and revisited to determine how much throttling should be done to it, something like an AdBlock list.