I know it may not be the most appropriate place to ask a question, but nevertheless: I was not
tracking Firefox 3 development much, but as it become available, I upgraded this morning
through my distribution upgrade mechanism (it's Slackware, so it should not differ much from
the "official" one), and found that it is freezing sometimes on larger images loads: it start
loading the image, and it displays some part of it, and then it freezes completely (not
possible to change to the other tab, or to press any of toolbar buttons, or anything else),
and then after couple seconds (or couple of tens of seconds sometimes), GUI becomes responsive
again. Very annoying; any suggestion?
Posted Jun 19, 2008 16:53 UTC (Thu) by MattPerry (guest, #46341)
[Link]
The mozillazine forums would probably be a better place to ask. But, having said that, did
the old one work fine? If so, then just downgrade.
Posted Jun 19, 2008 23:40 UTC (Thu) by Tet (subscriber, #5433)
[Link]
Downgrade? Hah! The mozilla developers don't believe in such things. Once you've tried it
once, you're screwed. For example, it changes your cookie file from plain text to an sqlite
db. Bummer if (like me) your home directory is NFS mounted across machines with a mix of FF1,
2 and 3. The first time you try FF3, you can't then go back to older versions without loss of
data :-( Unix is sadly very much a second class citizen in the mozilla world, which seems very
much focused on single user machines like Windows.
WTF?
Posted Jun 20, 2008 8:55 UTC (Fri) by Los__D (subscriber, #15263)
[Link]
How in the world does an upgrade changing file format have _ANYTHING_ to do with Unix being a
second class citizen?
Do you also run around screaming "2nd class citizen!!!", when X updates it's configuration
files? When Evolution do? When Postfix do? When g++ changes ABI?
Posted Jun 22, 2008 22:34 UTC (Sun) by nix (subscriber, #2304)
[Link]
Posted Jun 19, 2008 16:59 UTC (Thu) by rsidd (subscriber, #2582)
[Link]
It sounds like the fsync bug on ext3, that was "fixed" in rc2. (For me, things aren't quite
as smooth as in FF2 but it's a big improvement on previous versions of FF3.) But it shouldn't
manifest itself on images as far as I know. It is most obvious when typing in the address bar
and on some other operations involving sqlite.
The only image-related thing I can think of is colour management support, which apparently
causes a performance hit, but for that reason it is disabled by default and can only be
enabled via about:config. Perhaps slackware enables it by default.
Google for links.
Freezes
Posted Jun 21, 2008 22:37 UTC (Sat) by vonbrand (subscriber, #4458)
[Link]
In Fedora rawhide FF freezes due to a problem with spell checking. Turned that off, had no problems since.
fsync, maybe
Posted Jun 19, 2008 17:11 UTC (Thu) by elanthis (subscriber, #6227)
[Link]
Are you getting heavy disk access during this freeze? If so, it might be the fsync bug.
Although honestly, you shouldn't have this if you just installed 3.0 final.
If you're not getting fsync access, then it could very well be something else in the new
Firefox3 stack, such as cairo image rendering. If you're sure it only freezes on images, this
sounds rather likely: your video driver might need an update to handle Firefox's heavy
cairo/RENDER usage properly.
As said by another commentor, the correct place for you to ask this is MozillaZine or
Mozilla's Bugzilla.
fsync, maybe
Posted Jun 19, 2008 17:39 UTC (Thu) by asamardzic (guest, #27161)
[Link]
There is not much of the disk access throughout the freeze, but on the other side I noticed
the problem re-appears if I work for some time with other tabs, and then get back to the tab
where the image is loaded, so indeed it's probably something with the image rendering (BTW,
the color management is off)... In any case: thanks for all suggestions, and the pointer to
the proper place to ask for support - am trying my luck there, apologies once again for asking
the question here.
Do you have RandR and DRI enabled?
Posted Jun 19, 2008 19:03 UTC (Thu) by khim (subscriber, #9252)
[Link]
Recently found that if you enable OpenGL support in some versions of binary ATI drivers it disables DRI and RandR and Firefox 3 becomes SUPERslow. Firefox 2 is not affected.
Do you have RandR and DRI enabled?
Posted Jun 19, 2008 19:19 UTC (Thu) by rvfh (subscriber, #31018)
[Link]
Posted Jun 19, 2008 21:58 UTC (Thu) by nix (subscriber, #2304)
[Link]
Why would Firefox care about DRI? It's not doing 3D stuff, is it?
Do you have RandR and DRI enabled?
Posted Jun 20, 2008 9:47 UTC (Fri) by jamesh (subscriber, #1159)
[Link]
I'd guess that the problem is poor performance from the Render extension. It is possible that
disabling DRI also disables the acceleration of that extension, leading to the poor
performance.
Do you have RandR and DRI enabled?
Posted Jun 22, 2008 22:31 UTC (Sun) by nix (subscriber, #2304)
[Link]
I think only EXA accelerates Render to any extent, so if EXA is being
disabled (falling back to XAA) you *might* see a slowdown. (However, on my
distinctly aged Athlon desktop with a distinctly aged Radeon video card, I
see no performance problems with the render extension at all. However this
might be because, my failing memory tells me, the Radeon 9250 et al are
one of the few cards to have XAA-accelerated Render...)