Closed
Bug 174172
Opened 22 years ago
Closed 22 years ago
Mozilla uses 100% CPU while accessing applet
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: koonce, Assigned: joe.chou)
References
()
Details
The Craig troll may be irritating, but he does have a point. Clicking on the
referenced Applet throws Mozilla into a 100% CPU usage point on my machine,
forcing me to either kill the process (if I'm lucky) or reboot.
Sorry if this is a dupe, I couldn't find any matches for the URL.
I'm on Jaguar (10.2.1) and am using 1.2a.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2a) Gecko/20020910
-Brett
I got this one too, but it didn't force a reboot. I quit Mozilla by clicking
on the close button. The window disappeared, but my computer was still
running at 100% CPU usage. Bringing up Task Manager I could see that Moz was
still running so I killed it from there.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
![]() |
||
Comment 2•22 years ago
|
||
To OJI
Assignee: asa → joe.chou
Component: Browser-General → OJI
QA Contact: asa → pmac
Summary: BLUI Applet kills Mozilla → Mozilla uses 100% CPU while accessing applet
Reporter | ||
Comment 3•22 years ago
|
||
The applet doesn't bother IE, for the record.
It loads the CPU with this build, but the program remains usable:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910
-Brett
Reporter | ||
Comment 4•22 years ago
|
||
Also kills a nightly/my machine.
Mozilla 1.2b -
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021013
-Brett
Able to reproduce this using FizzillaCFM/2002101303 on 10.1.5. The question is,
are applets by their nature simply able to do this if badly written? Is Mozilla
responsible for making sure this doesn't happen? I don't know enough about Java
to say.
URL no longer exists. Resolving Invalid until someone can provide another URL
that causes this.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•