User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0 Build ID: 20150411030207 Steps to reproduce: I visited the about:performance special page. Actual results: I discovered that the displayed information updates every 2 seconds. But it is too hard for me to read so fast. Expected results: Please update the information less frequently. I suspect that every 10 seconds might be fine, though I haven't experimented to see whether or not this would be an acceptable update interval.
If you'd like to fulfill this feature request, please see line 157 of <chrome://global/content/aboutPerformance.js>. You'd probably want to change the number 2000 to some higher number.
Component: Untriaged → Performance Monitoring
OS: Windows 8.1 → All
Product: Firefox → Toolkit
Hardware: x86_64 → All
Indeed, to fix this bug, it is sufficient to change a single file: https://dxr.mozilla.org/mozilla-central/source/toolkit/components/aboutperformance/content/aboutPerformance.js?from=aboutPerformance.js#157 at the end of the file, replace `2000` with `10000`.
Whiteboard: [lang=js][good first bug]
I have submitted patches to other projects before, but never to anything Mozilla-related. Firefox is an established project, and so there's some established bureaucracy. There's a learning curve involved in submitting patches to a project with established bureaucracy. The Mozilla patch submission process, for example, includes more steps than the patch submission process for smaller projects. Because I've been busy lately, it would be unwise for me to go through this learning curve at this time. wrahman0, are you interested in submitting a patch?
Sure Jason, it looks like a very minor modification. I can submit a patch for it later today.
Increased the setInterval from 2 sec to 10 sec. Side note: I was wondering about the purpose of the setTimeout that wraps the setInterval. Shouldn't calling setInterval( ... , 10000 ) be sufficient to make the page update every 10 sec?
Attachment #8592360 - Flags: review?(dteller)
We display data on activity since the previous update. On startup, we immediately call `State.update()` to get initial data, then we wait a second before calling it again and displaying stuff. If we didn't wait one second, the calls to `State.update()` would be too close to each other, and our first dataset would be completely absurd.
Comment on attachment 8592360 [details] [diff] [review] bug1153877_increase_update_rate_to_ten_sec.diff Review of attachment 8592360 [details] [diff] [review]: ----------------------------------------------------------------- Looks good, thanks.
Attachment #8592360 - Flags: review?(dteller) → review+
Let's land this :)
(In reply to David Rajchenbach-Teller [:Yoric] (use "needinfo") from comment #8) > Let's land this :) aye sir :)
Assignee: nobody → wrahman0
Whiteboard: [lang=js][good first bug] → [lang=js][good first bug][fixed-in-fx-team]
Thank you all! In the latest nightly, about:performance is now much more usable.
Status: RESOLVED → VERIFIED
Whiteboard: [lang=js][good first bug] → [lang=js]
Sweet! I think you will like the play/pause feature even more!
You need to log in before you can comment on or make changes to this bug.