Closed Bug 1019025 Opened 10 years ago Closed 10 years ago

Small UI freezes while flash loads

Categories

(Core :: Graphics: Layers, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: pochu27, Unassigned)

Details

Running firefox from latest mozilla-central, compiled for GTK2 or GTK3. When playing a youtube video, during loading, flash shows a spinner. That spinner is freezing/stopping for short amounts of time, it's not spinning smoothly. This used to be fine (tested on Firefox 29 (iceweasel) from Debian), so looks like a regression. See also https://bugzilla.mozilla.org/show_bug.cgi?id=624422#c125 and https://bugzilla.mozilla.org/show_bug.cgi?id=624422#c126
After some investigations, this no longer looks like a regression. I tried to bisect on mozilla-central without much success as I as getting build failures when building old revisions (as in a few months old). So I went and tested nightlies and they were working ok. So perhaps this isn't actually a regression, but caused by something else, e.g. because of debug builds, that perform checks and so are slower, possibly causing this short glitches. I'll try an optimized build and see if that helps.
I see the freeze on debug/unoptimized builds only. Works fine for me with enabled optimization. Tested on Fedora 20/latest trunk. RPM packages are available at copr: http://copr-be.cloud.fedoraproject.org/results/stransky/FirefoxGtk3/fedora-20-x86_64/firefox-gtk3-32.0-1.fc20/ http://copr-be.cloud.fedoraproject.org/results/stransky/FirefoxGtk3/fedora-20-i386/firefox-gtk3-32.0-1.fc20/
Indeed, I can't reproduce when building with --disable-debug --enable-optimize. Should we keep this open? It seems normal that some debug checks or non-optimize code could cause such glitches.
Yeah, many things are just slow in debug builds.
OK, closing. It doesn't make a lot of sense to optimize non-optimized builds after all :)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.