Closed
Bug 102635
Opened 23 years ago
Closed 23 years ago
seventeen java_vm while browsing a URL
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
People
(Reporter: sergeisteshenko, Assigned: edburns)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.4+) Gecko/20011001 BuildID: 2001100108 Too many 'java_vm' when visiting a URL which requires Java and AFTER (when Java is already not needed): " 2324 root 9 0 20404 19M 5408 S 0.0 5.3 0:03 java_vm 2325 root 8 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2326 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2327 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2328 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2329 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2330 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2331 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2332 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2333 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2334 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2335 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2336 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2337 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2338 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2339 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm 2346 root 9 0 20404 19M 5408 S 0.0 5.3 0:00 java_vm ". 140 MBytes of memory are takedn for no good reason ! Reproducible: Always Steps to Reproduce: 1.download Mozilla - Java not yet installed 2.visiti sedmoycanal.com 3.monitor number of 'java_vm' in process table 4.visit any other URL not requiring Java 5.check again process table - 'java_vm' are still there Actual Results: slowness, unnecessary memory consumption Expected Results: 'java_vm' should go away when Java is not needed; why so many anyway ? I am not sure what the component is, but the problem is related to Java.
Comment 1•23 years ago
|
||
Those are threads, not processes. That means they share the same address space. The total memory usage is about 20MB. The java_vm is kept around after first use. Shutting it down and restarting it all the time would be a serious performance issue. So we lazily load it (don't load till the first time it's needed) then keep it for the duration of the session. I would say this in invalid, but over to OJI to decide.
Assignee: ashuk → edburns
Component: Java APIs for DOM → OJI
QA Contact: avm → pmac
*** This bug has been marked as a duplicate of 85319 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•