Bug 98848 - robohornet gets very slow if the page is backgrounded
Summary: robohornet gets very slow if the page is backgrounded
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Macintosh Intel Unspecified
: P5 Minor
Assignee: Kiran Muppala
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-09 21:14 PDT by Kiran Muppala
Modified: 2017-07-18 08:29 PDT (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kiran Muppala 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.
Comment 1 Maciej Stachowiak 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?
Comment 2 Kiran Muppala 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.
Comment 3 Kenneth Russell 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.
Comment 4 Ojan Vafai 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.