274504 - High CPU consumption in tiny Java applet

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[q1]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041206 MultiZilla/1.6.4.0b
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041206 MultiZilla/1.6.4.0b

See above.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.island.com/toolsresearch/index.asp
2. Under "Tools and Research", see "Bookviewer" is followed by "java | html"
3. Click on "java".
4. See Mozilla's CPU consumption hit 25-ish%, and stay there.
5. Now click in the "get stock" box in the Java applet and type a valid stock
symbol, like "AMD".
6. Click the "go" button.
7. Mozilla's CPU consumption continues at around 25%.
Actual Results:  
See above.

Expected Results:  
The applet is very simple, and should use very little CPU, especially when
simply idle (see step 4 under "steps to reproduce"). Safari uses less than 1% of
the CPU to run this applet.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Is Mozilla taking up the CPU, or is Java?  Please check with a reasonable system
load application (or at least 'top' in a Terminal.app window).  Note that Safari
uses a different version of Java from Mozilla; the Safari version is not exposed
by Apple last I checked, so Safari is using undocumented OS apis to use it...

Comment 2

[q1]

(In reply to comment #1)
> Is Mozilla taking up the CPU, or is Java?  Please check with a reasonable system
> load application (or at least 'top' in a Terminal.app window).  Note that Safari
> uses a different version of Java from Mozilla; the Safari version is not exposed
> by Apple last I checked, so Safari is using undocumented OS apis to use it...

It's Mozilla using the CPU, not Java.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.