Closed Bug 766280 Opened 12 years ago Closed 12 years ago

Performance regression / application not responding frequently in 20120614 nightly builds on Windows (slow network access, UI rendering, no UI interactivity)

Categories

(Firefox :: General, defect)

16 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox16 - ---

People

(Reporter: beltzner, Unassigned)

Details

Recent Firefox Nightly builds feature unusably slow performance. It seems to be blocked on network access or on drawing the user interface elements. All interaction with the UI is impossible in this state, and the application is frequently reported by Windows to be "Not Responding" - see the video, below (I'll also try to attach it)

http://beltzner.ca/display-bug.webm

A regression hunt on my local system pinpointed this performance regression to the June 14th build; in the video above I'm using the June 13th build to show Firefox in good working order, then the 14th to show bustage. Same thing happens with a new or existing profile. Here's the regression range:

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=880f30ecdf6b&tochange=983b91e5aa17

I initially suspected Azure, as the problem isn't happening on all Windows machines and I know that I have an older graphics driver. However, switching gfx.canvas.azure.enabled to false has no effect.

(cc'ing Rob and Ehsan as there are some Windows updater changes in that range as well, but I can't see how they'd be related ...)
(Can't attach the video, it's 600kB bigger than maximum attachment size; use the link, instead!)
Ah this is bad.  Any chance you could use the hourly builds to get a better regression range?
My suspect for this is http://hg.mozilla.org/mozilla-central/rev/1100e41af4e6.  The only evidence I have for this is managing to break during one of these hangs in a debugger and seeing us deep in InternetQueryOptionW.
(In reply to Mike Beltzner [:beltzner] from comment #0)
> I initially suspected Azure, as the problem isn't happening on all Windows
> machines and I know that I have an older graphics driver. However, switching
> gfx.canvas.azure.enabled to false has no effect.

Oops! That's not the right pref. You want gfx.content.azure.enabled.
The try build from comment 4 (backout of bug 759036) shows the same effects, so we can scratch that off the list of potential culprits. I can bring my machine into the Mozilla Toronto office on Thursday afternoon if Joe or Ehsan want to prod at it a little bit ...
Please do.
Well, son of a b. I came into the office, and could no longer reproduce. The only thing that had changed was that I installed a bunch of Windows updates, and since that restart, my display driver has yet to crash. I'll wait for it to do that and see if that causes the problem.
Returning tracking-firefox16 to "?" to reprioritize this as I can't get it to happen again. I didn't fake the video above, so it was happening, and khuey said he was seeing something similar, but I can't get it to happen again so happy to drop the priority of it.

If it crops up more, I'll add more info.
OK, I'm totally stumped. Closing for now as it's been several days and the problem hasn't come back :(
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.