Mozilla throbber is unable to reliably animate 32x32 image at 10 FPS. On hardware where games can easily run 3D 800x600 x 50fps this is 100% pathetic. 100ms is also an acceptable maximum UI response time.
This can be a meta bug for all issues related to user interface latency.
Depends on: 15122
Keywords: nsCatFood, perf
*** Bug 99054 has been marked as a duplicate of this bug. ***
Marko, I think, you should morph this bug. This is an architecural problem: Most of the Mozilla code, incl. the UI, runs in one thread. If any function needs more time, the UI is frozen. (I don't know, why this has been coded that way.) Some of the bugs you marked as blockers are functions that happen to take longer than a second. But that is just a coincidence - if these bugs are fixed, others will probably come up. The underlying problem is the lacking threading. Also, the throbber is spinning smoothly is just one symptom. At the same time, *all* of the UI is frozen. I think, this should be a bug to decouple the UI from the rest of the code. This is a major architectural rework, so don't expect it to get fixed before 1.0.
Ben, that's already filed, I believe
Ben, using threads to do CPU consuming jobs is good. But some things just can't be done that way. Since layout drives the entire GUI it can't be just put into a separate thread (using thread per toplevel window might be doable -- using fork to start a new window keeps coming back to my mind ;). Bug 66907 and but 77051 are like these. Not much sense in using a separate thread for them.
No offense intended, but this seems more like your bug, and frankly, my name is on too many meta bugs, which generate more notifications than I can deal with at times.
Assignee: hyatt → Marko.Macek
QA Contact: jrgm → nobody
A unresponsive UI is very annoying for users. Any news on that (threading) ?
is this really thought to still be a problem, given the changes made to throbber animation in recent releases (was it v3.6? I forget which)
wsmwk, FF 4.0 is worse than ever in the last 5-10 years. Probably because of JS engine garbage collection or something like that. That said, I don't think this bug is the right vehicle, as the throbber is just one symptom.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → DUPLICATE
Whiteboard: [closeme 2011-04-15]
Duplicate of bug: 308158
You need to log in before you can comment on or make changes to this bug.