NEW98848
robohornet gets very slow if the page is backgrounded 
https://bugs.webkit.org/show_bug.cgi?id=98848
Summary robohornet gets very slow if the page is backgrounded
Kiran Muppala
Reported 2012-10-09 21:14:01 PDT
https://bugs.webkit.org/show_bug.cgi?id=98474 introduced throttling of DOM timers on hidden pages by aligning them to 1 second intervals. Kenneth Russell, commented in that bug that a known issue with timer throttling in chromium is robohornet benchmark (www.robohornet.org) slowing down if put on a background tab, even if it has popup windows which are in the foreground. http://code.google.com/p/chromium/issues/detail?id=152077. Testing on mac, showed that hidden page timer alignment also exhibits the same behavior. Filing this bug to figure out how to address this issue.
Attachments
Add attachment proposed patch, testcase, etc.
Maciej Stachowiak
Comment 1 2012-10-09 22:59:07 PDT
Is this actually a bug? I'd expect benchmarks that rely on timers to run slower when in a background tab, with any form of background tab timer throttling. We could add a special case to avoid throttling background (or otherwise non-visible) pages with visible popups, but is there a reason that is actually important?
Kiran Muppala
Comment 2 2012-10-09 23:55:25 PDT
(In reply to comment #1) > Is this actually a bug? I'd expect benchmarks that rely on timers to run slower when in a background tab, with any form of background tab timer throttling. > > We could add a special case to avoid throttling background (or otherwise non-visible) pages with visible popups, but is there a reason that is actually important? No, I didn't think this is important. In fact I wasn't even sure if this needed to be fixed. I just filed the bug to not loose track of it. Lowered the priority of the bug.
Kenneth Russell
Comment 3 2012-10-10 10:54:55 PDT
I suspect that the authors of the robohornet benchmark consider this more than a minor issue. CC'ing a couple.
Ojan Vafai
Comment 4 2012-10-10 12:34:53 PDT
I think we should just change robohornet to listen to visibilitychange events and return an error to the user if the page is ever hidden.
Note You need to log in before you can comment on or make changes to this bug.