Closed
Bug 736602
Opened 13 years ago
Closed 12 years ago
Change inactive tab timer clamp setting to something higher than 1hz
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox14 fixed, firefox15 fixed, blocking-fennec1.0 +)
RESOLVED
FIXED
People
(Reporter: mfinkle, Assigned: kbrosnan)
References
Details
Attachments
(3 files, 1 obsolete file)
810 bytes,
patch
|
mfinkle
:
review+
akeybl
:
approval-mozilla-aurora+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
853 bytes,
patch
|
blassey
:
review-
blassey
:
approval-mozilla-aurora-
blassey
:
approval-mozilla-beta-
|
Details | Diff | Splinter Review |
821 bytes,
patch
|
mfinkle
:
review+
blassey
:
approval-mozilla-aurora+
blassey
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Inactive tabs clamp the timers to 1hz. We could clamp them higher and save some battery life. Suspend forever is not an option, so we need to pick a "high" value.
What value? 1 day?
The pref is "dom.min_background_timeout_value" (see bug 633421)
Updated•13 years ago
|
OS: Linux → Android
Hardware: x86 → ARM
Updated•13 years ago
|
blocking-fennec1.0: --- → ?
Reporter | ||
Comment 1•13 years ago
|
||
We'd like to get some data on power usage versus clamping frequency. The A-team is working on power monitoring solutions.
Updated•13 years ago
|
blocking-fennec1.0: ? → -
Updated•13 years ago
|
blocking-fennec1.0: - → ?
Reporter | ||
Comment 2•13 years ago
|
||
For the record, I have no issue with bumping this value up, but I do not want to use the pref to disable timers completely. Note that the value affects any tab that is not the selected tab when Firefox is in the foreground and all tabs when Firefox is in the background.
I think there is a bug about disabling timers, JS and events after a period of being in the background built into the platform. I think that's a better approach and I don't want to use some front-end hacks to simulate that either.
We should also provide a way for users to allow pages to request running in the background.
Again, what value should we use? I see no harm in bumping the threshold to anything in the 10 to 30 second range. Maybe up to 60 seconds.
blocking-fennec1.0: ? → -
Reporter | ||
Comment 3•12 years ago
|
||
Let's test with a 15min throttle. A test page can be found here:
http://people.mozilla.org/~kgupta/bug/761731.html
Assignee: nobody → kbrosnan
blocking-fennec1.0: - → +
Assignee | ||
Comment 5•12 years ago
|
||
Attachment #632069 -
Flags: review?(mark.finkle)
Comment on attachment 632069 [details] [diff] [review]
patch to increase the timeout to 15m
Review of attachment 632069 [details] [diff] [review]:
-----------------------------------------------------------------
Doesn't this just add an empty line?
Assignee | ||
Comment 7•12 years ago
|
||
Comment on attachment 632069 [details] [diff] [review]
patch to increase the timeout to 15m
Doh qupdate why do you hate me.
Attachment #632069 -
Attachment is obsolete: true
Attachment #632069 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 8•12 years ago
|
||
Attachment #632085 -
Flags: review?(mark.finkle)
Updated•12 years ago
|
Attachment #632085 -
Attachment is patch: true
Reporter | ||
Comment 9•12 years ago
|
||
Comment on attachment 632085 [details] [diff] [review]
a patch with some code
I assume this has a noticeable effect on the test file
Attachment #632085 -
Flags: review?(mark.finkle) → review+
Comment 10•12 years ago
|
||
Comment on attachment 632085 [details] [diff] [review]
a patch with some code
[Triage Comment]
Approving for Aurora and Beta in preparation for the B7 go to build. We can also test in QA with tinderbox builds in the morning.
Attachment #632085 -
Flags: approval-mozilla-beta+
Attachment #632085 -
Flags: approval-mozilla-aurora+
Comment 11•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/23e8e357b19d
https://hg.mozilla.org/releases/mozilla-aurora/rev/6ccff991c3b1
https://hg.mozilla.org/releases/mozilla-beta/rev/e1f1b8aa81f8
Status: NEW → RESOLVED
Closed: 12 years ago
status-firefox14:
--- → fixed
status-firefox15:
--- → fixed
Resolution: --- → FIXED
Comment 12•12 years ago
|
||
Attachment #632118 -
Flags: review?(mbrubeck)
Reporter | ||
Comment 13•12 years ago
|
||
Might be better to just force the pref back to normal for tests:
http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in#309
Reporter | ||
Comment 14•12 years ago
|
||
Comment on attachment 632118 [details] [diff] [review]
follow up to disable a test that times out
I'm OK with disabling the test in the short-term, but I think we need to reset the timeout pref for mochitests using the link I posted.
Attachment #632118 -
Flags: review?(mbrubeck) → review+
Comment 15•12 years ago
|
||
Comment on attachment 632118 [details] [diff] [review]
follow up to disable a test that times out
[Approval Request Comment]
Risk to taking this patch (and alternatives if risky): Android-only test-only change to silence a failing test.
String or UUID changes made by this patch: None.
Attachment #632118 -
Flags: approval-mozilla-beta?
Attachment #632118 -
Flags: approval-mozilla-aurora?
Comment 16•12 years ago
|
||
Attachment #632134 -
Flags: review?(mbrubeck)
Reporter | ||
Comment 17•12 years ago
|
||
Comment on attachment 632134 [details] [diff] [review]
patch to change pref for tests
I think this method is preferred
Attachment #632134 -
Flags: review?(mbrubeck) → review+
Comment 18•12 years ago
|
||
Updated•12 years ago
|
Attachment #632118 -
Flags: approval-mozilla-beta?
Attachment #632118 -
Flags: approval-mozilla-beta-
Attachment #632118 -
Flags: approval-mozilla-aurora?
Attachment #632118 -
Flags: approval-mozilla-aurora-
Updated•12 years ago
|
Attachment #632118 -
Flags: review+ → review-
Comment 19•12 years ago
|
||
Comment on attachment 632134 [details] [diff] [review]
patch to change pref for tests
[Triage Comment]
Attachment #632134 -
Flags: approval-mozilla-beta+
Attachment #632134 -
Flags: approval-mozilla-aurora+
Updated•9 years ago
|
Blocks: background-data
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•