java_vm erratically starts using CPU time



Core Graveyard
Java: OJI
16 years ago
8 years ago


(Reporter: Peter Weilbacher, Assigned: Joshua Xia)


Firefox Tracking Flags

(Not tracked)




16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722
BuildID:    2002072204

Every now and then I see the red bar in xosview grow (giving the sys time). This
happens erratically but seems to be related to the java_vm process started by
the Java-Plugin of Mozilla.

I cannot reproduce it. But just now I had a page without Java just sitting there
and it happened. Just to make sure that there really was no Java activity I
closed all windows and tab but one, and loaded about:plugins there. Several
minuted before I had visited, but it does
not seem to matter which page loaded the java_vm.

Starting top I saw this:
25454 25450 weilbach   9   0    13  109M 20068   12 8004  11M  3900 S     9.5 
4.7   1:42 java_vm

Reproducible: Couldn't Reproduce

Comment 1

15 years ago
Peter, are you still experiencing this problem? Can you reproduce it with a
current copy of mozilla and java?

How long do these high-cpu periods last? If they're short, you may just be
seeing the java garbage collector activate.

--> OJI.
Assignee: idk → joshua.xia
Component: Java-Implemented Plugins → OJI
QA Contact: avm → dsirnapalli

Comment 2

15 years ago
I think I still see this from time to time with Mozilla 1.3 and Java 1.4.1_01
(hope this is current enough). But I now have a way faster machine than when I
reported this bug, so it does not worry me much any more.

But if this is the garbage collector should I not see some output of this in the
Java-Console? And does the gc really start when I have not visited any Java
related webpage for several minutes or hours?

Comment 3

15 years ago
Reporter can you reproduce this bug with a newer build (1.4 final) and Java 1.4.2?
If not, then please close this bug as worksforme. Thanks.
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:

Comment 5

13 years ago
I think this is still present in the newest versions but on a fast machine this
is not as big a problem any more, plus I am hardly using the Java plugin any
more. Additionally, I don't have the impression that anyone working on the Java
plugin has any interest in this, so I just resolve it WFM...
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME


8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.