98848 2012-10-09 21:14:01 -0700 robohornet gets very slow if the page is backgrounded 2017-07-18 08:29:28 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Mac (Intel) Unspecified NEW P5 Minor --- 1 cmuppala cmuppala ap fishd jamesr kbr mjs simon.fraser tonikitoo oldest_to_newest 738491 0 cmuppala 2012-10-09 21:14:01 -0700 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. 738580 1 mjs 2012-10-09 22:59:07 -0700 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? 738644 2 cmuppala 2012-10-09 23:55:25 -0700 (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. 739118 3 kbr 2012-10-10 10:54:55 -0700 I suspect that the authors of the robohornet benchmark consider this more than a minor issue. CC'ing a couple. 739216 4 ojan 2012-10-10 12:34:53 -0700 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.