I knew that Java and Netbeans could be memory hogs, but 16 million TB (16 exabytes) is a bit much. Good thing I have virtual memory! (I didn't alter the image, but clearly it's a bug with Activity Monitor and/or OS X 10.5.2.)
Charles.
Saturday, March 29, 2008
Netbeans is a memory hog?
I was looking at Activity Monitor on my iMac, and I couldn't read the size entry for the Netbeans process that was running. So, I selected it and got a detail report:
I knew that Java and Netbeans could be memory hogs, but 16 million TB (16 exabytes) is a bit much. Good thing I have virtual memory! (I didn't alter the image, but clearly it's a bug with Activity Monitor and/or OS X 10.5.2.)
Charles.
I knew that Java and Netbeans could be memory hogs, but 16 million TB (16 exabytes) is a bit much. Good thing I have virtual memory! (I didn't alter the image, but clearly it's a bug with Activity Monitor and/or OS X 10.5.2.)
Charles.
Subscribe to:
Post Comments (Atom)
3 comments:
The Virtual Memory Size has nothing to do with memory size occupied by a program. Look at the Private Memory Size and Real Memory Size and you should have a more reliable value for memory use.
I know the difference between real and physical memory, and my machine was running fine under the circumstances, so it was clearly an error. I was just pointing out (tongue in cheek) the absurd value of 16 exabytes. Virtual, physical, or disk - that's just a crazy number. (At least it is in 2008. By 2020, maybe our microwave ovens will have that much memory.)
Charles.
You said: "I knew that Java and Netbeans could be memory hogs, but 16 million TB (16 exabytes) is a bit much."
So I thought that you meant that Virtual Memory Size was the size a software occupied in memory. Sorry.
And yes, that is a crazy number.
Post a Comment