CODEWITHSUNDEEP
javascriptgoogle-chrome
Trevor Dixon
Trevor Dixon

Reputation: 24352

Chrome tab crashing / hanging after brought on foreground being long time on background

I've got a page that shows real-time statistics. It runs a lot of javascript, makes a lot of HTTP requests, renders SVG charts every few seconds using D3.js, has a lot of CSS animations, and rearranges the DOM frequently.

As long as the page is focused, it runs smoothly. If I switch to another tab and come back later, there's often a short pause where the page seems to be frozen before the view suddenly seems to rerender and the page becomes usable again. The longer the tab has been backgrounded, the longer this pause is. If the tab has been in the background for a very long time (hours) and I switch back to it, it will be frozen for a long time then crash.

All these behaviors are observed in Chrome. I haven't tested much in other browsers.

What isn't Chrome doing while the tab is in the background, and what is it doing during that pause when I first switch back to the tab?

UPDATE:

I'm also doing some jQuery animating. This answer and this one may be relevant.

According to that first answer:

"Inactive browser tabs buffer some of the setInterval or setTimeout functions."

stop(true,true) will stop all buffered events and execute immediatly only the last animation.

I've added a call to .stop(true, true) in my code, and at least for short trips away from the tab, I'm not detecting a hiccup. I need to leave it in the background for a long time and test it before I can tell if it made significant difference.

Upvotes: 12

Views: 4042

Answers (2)

Lasitha Petthawadu
Lasitha Petthawadu

Reputation: 763

We had a similar issue with SVG graphs and managed to solve it using Page Visibility API introduced with HTML5. If anyone stumbles upon such an issue please refer to the following article Using the Page Visibility API

What we managed to do was to suspend all SVG rendering activities when the browser window is not visible. This managed to stop the tab from crashing.

Upvotes: 11

bonbonez
bonbonez

Reputation: 6848

Yes, it's typical behavior of Chrome browser.

I guess that while your tab is in background, Chrome places all tab data on "back shelf" to clear "front shelf" that works much faster. I know, it sounds unprofessionally, but i hope that you understood.

I think it is very hard to solve this problem in your case (because you are using a lot of manipulations with graphic).. but maybe this method will save you (i had never tested it before):

Every time you update your statistics (or do some highload calculations), you can save a timestamp. Then, when you update your statistics again, you can substract that old timestamp of the new timestamp. And, if you see that the difference between timestamps is very big, use setTimeout() function before next update. Maybe, it will prevent Chrome's chash.

Upvotes: 2

Related Questions