Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Tonight, while my computer was devoting most of its CPU to other tasks, Chrome decided that every tab that was using a plugin had crashed.

In Firefox there's a configuration setting for the number of seconds that a plugin is allowed to be unresponsive before the tab is considered "crashed", but I haven't been able to find the analogous setting in Chrome.


share|improve this question
Doubt Google would ever do something like that. Just goes to show you, even on a computer you have to let go before it's pried out of your cold, dead, RAM. –  digitxp Sep 3 '10 at 4:14

1 Answer 1

There is not currently a way to do this because Chrome’s mission is to provide a minimal interface by doing things correctly so that users don’t have to configure options or make choices. (Of course when it doesn’t do things correctly, preventing the user from setting an option to fix it is annoying.)

I’ve submitted an issue to request a way to set the timeout, but like digitxp said, chances are that they won’t implement it (unfortunately, they have a tendency to think that their choices are always the right ones).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.