This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 76625 - Does the memory meter really mean anything?
Summary: Does the memory meter really mean anything?
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P4 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-19 23:03 UTC by ssoong
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ssoong 2006-05-19 23:03:13 UTC
NetBeans IDE Dev (Build 200605171800)1.5.0_05
Java HotSpot(TM) Client VM 1.5.0_05-b05
Windows XP version 5.1 running on x86 en_US (nb)
================================================

The memory meter on my NB session currently shows 33.8/72.2 MB,
but windows task manager shows jave.exe
Mem Usage = 156,640K, VM Size = 155,808K.

I don't see any relationship between the two sets of values.
Is memory meter being dishonest about memory usage?
(Like some car makers about their mpg, by skipping
some criteria).

What does it actually map?

When I start tomcat, a new java process is started,
as indicated by task manager. Does memory meter
take that memory used into consideration?

It was actually shown by task mgr as Mem Usage = 148MB
until I clicked on memory meter, hoping to bring down
memory usage. Instead, it went up to 156,640K
(grr... my teeth gnashing on finger nails now)!
Hmm ....
Comment 1 ssoong 2006-05-22 14:45:08 UTC
typo: jave.exe should have been java.exe .
Comment 2 Petr Hrebejk 2007-06-22 14:40:20 UTC
1) Not sure why this is assigned to java. Should you reopen the issue assign it to core.
2) Sure it does mean something. It shows size of the heap in the VM running the ide.
3) Sure you see something else. This is because the task manager shows how much the VM consumes. Including, the VM
itself, loaded classes, some native buffers etc. This is very different from the heap size.
4) Tomcat is probably started in different VM, so no it does not take it into account
5) Should the memory meter be changed. No way! :-)
Comment 3 Quality Engineering 2007-09-20 10:47:20 UTC
Reorganization of java component