Closed Bug 45617 Opened 24 years ago Closed 24 years ago

[FEATURE] Mozilla becomes unresponsive while rendering

Categories

(SeaMonkey :: General, enhancement, P3)

x86
Linux
enhancement

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: rosmo, Assigned: asa)

Details

(Keywords: perf)

When rendering, for example, a page with a big table, Mozilla becomes unresponsive during the rendering. No toolbar buttons can be pressed, or menus accessed or other browser windows used. Also the browser windows don't update properly (other windows draw over them). Mozilla/5.0 (X11; U; Linux 2.2.16 i586; en-US; m17) Gecko/20000716
Adding perf keyword.
Keywords: perf
See also mostfrequent bug 17325 "Limit number of incremental reflows".
Comments on bug 17325 say: "Ideally (sorry), we'd do more reflows, not fewer, for big complicated tables, in order to service UI events more often. If a big reflow takes too long away from the event loop, the UI starves." It doesn't seem like the proper solution, why block the UI while reflowing? The UI should never block - otherwise the user might think the browser crashed.
well, all browsers (4.7, ie) do that when takign ups lots of memory, you can't really do this that easily, if at all. yes, mozilla does it more than the others, but that is due to memory bugs, this is not a feature, but is a nessecity. And therefore invalid, as this is optimisation work
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
makes sense, verifying
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.