Closed
Bug 783015
Opened 12 years ago
Closed 12 years ago
Chrome refreshdriver runs all the time
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla17
People
(Reporter: smaug, Assigned: smaug)
References
Details
(Whiteboard: [qa-])
Attachments
(2 files)
1.69 KB,
patch
|
khuey
:
review+
|
Details | Diff | Splinter Review |
1.68 KB,
patch
|
Details | Diff | Splinter Review |
I was randomly checking where to optimize responsiveness and noticed that the chrome refresh driver runs all the time at full speed. It happens even if there is just one Firefox window open and the only page is about:blank. (in that case the content refreshdriver doesn't run) (Another thing not clear to me at all is why we have separate refreshdriver for content and chrome)
Assignee | ||
Comment 1•12 years ago
|
||
Looks like we run the driver all the time because there are 2 image requests. Investigating ...
Assignee | ||
Comment 2•12 years ago
|
||
chrome://browser/skin/tabbrowser/connecting.png chrome://browser/skin/tabbrowser/loading.png are all the time in the refresh driver.
Assignee | ||
Updated•12 years ago
|
Component: Layout → General
Product: Core → Firefox
Assignee | ||
Comment 3•12 years ago
|
||
Not sure if this is a layout bug or Firefox/Toolkit bug.
Comment 4•12 years ago
|
||
These images are used by <xul:image> tags that have a list-style-image assigned. If the tab's not busy they're hidden using 'display: none'. https://mxr.mozilla.org/mozilla-central/source/browser/base/content/tabbrowser.css#44 I suspect a layout bug here.
Assignee | ||
Updated•12 years ago
|
Component: General → Layout
Product: Firefox → Core
Assignee | ||
Comment 5•12 years ago
|
||
Back to layout. It really should remove imgIRequests from refreshdriver if those won't be painted.
Assignee | ||
Comment 6•12 years ago
|
||
So I think this is because ImageLoader registers image request even if there isn't any frames using it. Trying to fix this.
Assignee: nobody → bugs
Assignee | ||
Comment 7•12 years ago
|
||
Assignee | ||
Comment 8•12 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=43ad063bd61c
Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 652268 [details] [diff] [review] WIP Breaks animated backgrounds.
Attachment #652268 -
Attachment is obsolete: true
Assignee | ||
Comment 11•12 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #9) > Comment on attachment 652268 [details] [diff] [review] > WIP > > Breaks animated backgrounds. Or maybe not. They are broken anyway, Bug 783220
Assignee | ||
Updated•12 years ago
|
tracking-firefox17:
--- → ?
Assignee | ||
Updated•12 years ago
|
Attachment #652268 -
Attachment is obsolete: false
Attachment #652268 -
Flags: review?(khuey)
Assignee | ||
Comment 13•12 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=67f1c1ef4586
Updated•12 years ago
|
Attachment #652268 -
Flags: review?(khuey) → review+
Assignee: khuey → bugs
Assignee | ||
Comment 14•12 years ago
|
||
actually use presContext and don't recall the method.
Assignee | ||
Comment 15•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e33c175f6807
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-firefox17:
--- → fixed
Target Milestone: --- → mozilla17
Comment 16•12 years ago
|
||
Can someone please advise QA how to verify this bug is fixed for Firefox 17?
Whiteboard: [qa?]
Assignee | ||
Comment 17•12 years ago
|
||
that is hard. I profiled FF, and added some printfs to refreshdriver to figure out this. but I haven't seen this after the fix.
Comment 18•12 years ago
|
||
Okay, thanks Olli. I'm going to flag this [qa-] meaning QA won't allocate resources to trying to verify this fix. If you or someone else finds a way to reliably verify this, please do so. Thank you.
Whiteboard: [qa?] → [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•