166979 - Extremely slow/bugged performance with Quick Launch on (was: after loading a Java Applet)

Status: RESOLVED WORKSFORME

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

Description

[Max Nokhrin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Please note that I have only been able to reproduce this problem on Celeron
733Mhz, but not a Pentium 2+ system.

After I load up a Java Applet (in this case, the chess room at www.pogo.com) and
Java gives several warnings or errors, Mozilla becomes unbaringly slow, taking
up over 50% of the processor. 

Sometimes (about 1 in 5 times): When I close all Mozilla windows, I still have
to use teh Task Manager to kill a mozilla.exe process that doesn't close
autimatically when I close all windows.

Reproducible: Always

Steps to Reproduce:
1. Open up a Java Applet that gives a warning or an error.
2.
3.

Actual Results:  
After several seconds, the window with the Applet froze and Mozilla started
taking up over 50% of the processor usage.


I'm using a Celeron 733Mhz, 386MB RAM, Windows 2000 SP3, 30GB HD. 

Please note that I haven't been able to reproduce this on a Pentium 2+ 500Mhz+
system.

Comment 1

[Matthias Versen [:Matti]]

which JRE Do you use ?

Comment 2

[Max Nokhrin]

I have JDK 1.4.0. 

I have been able to reproduce the crash on a Pentium 3 933Mhz, 512MB RAM
computer running Windows 2000 SP3. However, this didn't involve Java. I opened a
file download that I left overnight. In the morning, I noticed that Mozilla was
stuck at 90%, taking up 100% of the processor. Afterwards, there were more
crashes. I think that the bug is in the cache size that I set.

I set *very* small cache size:

1024 memory
2048 disk

Mozilla seems to be unable to function properly with so little cache. When I set
the cache to

8192 memory
10240 disk

Mozilla seems to be working better.

I set cache to small sizes because in my experience, the browser had no other
choice but to download the latest version of the page from the server. 

Comment 3

[Max Nokhrin]

The error seems to actually be in allowing Mozilla to stay in memory. As long as
this option is enabled, Mozilla will crash often, even with a larger cache size.
It just crashed several times repeatedly until I killed it completely.

I think that it's probably this feature that is bugged.

Comment 4

[Max Nokhrin]

After more testing, I'm more sure that this is because of the Quick Launch.

Comment 5

[Max Nokhrin]

Changing component to Quick Launch

Comment 6

[Matthias Versen [:Matti]]

.

Comment 7

[Grace Bush]

Confirm with my Win 2k system PentiumIII 500mhz
with QL  enabled, it takes 22 seconds to launch the chess board
with QL off, it takes 11 seconds

cannot reproduce crash

Comment 8

[Max Nokhrin]

I haven't been able to reporudce the crash evey time also. However, once it
crashes once, it starts crashing constantly.

Comment 9

[Max Nokhrin]

I'm still seeing this randomly. I'm presently using 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Comment 10

[Max Nokhrin]

Still there in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040514

Comment 11

[Gabriel Chadwick]

This wfm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050409 Firefox/1.0+