Closed Bug 695118 Opened 13 years ago Closed 11 years ago

When switching tabs to google reader 30% of our drawing time is spent on chrome

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: taras.mozilla, Unassigned)

References

Details

We should not invalidate entire chrome when switching tabs. IE prioritizes updating content and tabs lag significantly.
I don't think this is specific to D2D.
Component: Graphics → Layout
QA Contact: thebes → layout
Summary: D2D: When switching tabs to google reader 30% of our drawing time is spent on chrome → When switching tabs to google reader 30% of our drawing time is spent on chrome
With the new google reader I have been getting large pauses (~2s) when switching to a google reader app tab. FF basically hangs during this time and is unresponsive. This has also been sometimes (randomly) associated with large increases in heap-unclassified in about:memory. This is on today's moz-central win32 nightly build. D2D/D3D10 on. Win 7 64bit. E8500 based system with ATI HD4650 GPU. Latest drivers.
DB, and if you set gfx.direct2d.disabled to true, does performance improve?
After trying it for ~ 30 mins, it seems that the pauses on tab switching are about half as long (bit less than 1s) with HWA off (gfx.direct2d.disabled set to true).
(In reply to DB Cooper from comment #4) > After trying it for ~ 30 mins, it seems that the pauses on tab switching are > about half as long (bit less than 1s) with HWA off (gfx.direct2d.disabled > set to true). So turns out the problem in my case was that I set windows to use the "power saver" power plan. Apparently that makes the intel GFX driver go into "draw slowly" mode. We should disable direct2d, at-least on intel chips when this setting is on. DB, what power plan are you using Balance or "High Performance" plans help?
I was using "High Performance". Google Reader has been updated (at least) twice since then, and this is no longer a problem for me.
I'm using firefox 12a2, the problem still occuring. Besides the lag on switch tab, memory consumption increase as well.
any new progress of this bug?
Google Reader has been discontinued.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.