I found this problem yesterday, and it also exists in today's nightly build. I tried to check bug http://bugzilla.mozilla.org/show_bug.cgi?id=26796 , but browser at the http://www.sports.ru went even futher - stop responding, and even all other programs could not get focus. There were no response to mouse clicks not only in mozilla programs, but there was no response to _any_ mouse clicks. Well, that wasn't total OS crash, since Ctrl+Alt+Del and EndTasking Mozilla brought everything to normal conditions.
Confirmed with the 2000-02-22-08-M14 nightly binary on Windows NT; 64MB memory, P120, modem connection. It would be easy for a user to come to the conclusion that Mozilla had hung, but what is happening here is no more than the ordinary (for complex pages) grind just before the [Stop] button greys, much worse than usual. The page has many fast animated gifs. The non-responsiveness is due to tens of seconds of 90%+ CPU usage, but during this period both Mozilla and other Apps did respond, albeit with delays of many seconds and very slowly. After the page loads, responsiveness returns to normal. It's very unlikely that most users with older, slower machines would wait that long, however. This could very well be the same issue as in bug 26028, "extremely long delay after loading page". I've seen the same problem loading a local copy of the MySQL manual (~1MB of straight clean HTML)
Assignee: cbegle → troy
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout
Ever confirmed: true
QA Contact: asadotzler → petersen
Summary: Browser stops responding → Browser stops responding for extended period
Assignee: troy → vidur
Wondering if this could have any similarities to bug 18189, "[INC CONTENT SINK] select scrollbars display multiple times", M15. Retested with the 2000-02-28-08 binary on WinNT on a faster machine, the processor bog seemed to coincide with the final reflow of the page. On reload, with the files coming out of the cache and presumably being parsed before the first incremental reflow could happen, there was no problem with responsiveness at all.
Tested with Build 2000-05-05-13 on a Pentium II 350 MHz running on Windows 98 SE and couldn't reproduce the problem. Is my machine too fast, or has the problem been fixed?
Seems like the performace problem has been fixed. There is a crash on the 6/15 build. Investigating...
No crash, actually. Marking the bug FIXED.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Fixed in the July 14th builds.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.