Any page that uses a decent amount of JavaScript, actually. Occasionally it's just a standard "Sad Tab" page, but usually it's a "Scripts on this page used up too much memory, refresh to re-enable scripts." This only happened in more recent builds; in the past I never got the "script using too much memory" bar. Whether this is because the bar was unimplemented or not, I do not know.
On Dec 1, 12:33 pm, Rafael Weinstein <[email protected]> wrote: > What page(s) are you visiting that are habitually crashing the Tab? > > It'd feel like a bit of a defeat to add a 'crashed' property to the > tab object (as opposed to addressing the cause of the crashes). > > > > On Thu, Nov 26, 2009 at 2:32 PM, Pauan <[email protected]> wrote: > > Right now, the only two states in tab.status are "loading" and > > "complete". In an extension of mine, I would like to reload a page if > > it crashed (i.e. Sad Tab). Unfortunately, I have been unable to detect > > when a page has crashed or is otherwise unresponsive. My solution so > > far has been to periodically refresh the page every x minutes, but > > this is obviously far from ideal. It would be nice if there were a > > "crashed" status, or similar. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Chromium-extensions" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/chromium-extensions?hl=en. -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
