But is that memory allocated out of the chunk of VM reserved as the HEAP?
I doubt it... I don't think it even blongs to the same process does it?
Seems to me that it would have to belong to the Xserver's process... in
the Xserver's address space and potentially on the Xserver's machine
(as in a different machine than the JVM).By the same token if I go into native code by way of JNI and malloc 28Mb
of main store, yes it comes out of the process address space that the JVM
is running in, but it does not come out of the *heap*. The only thing that
GC tracks in terms of memory usage is the amount of it's _reserved_ memory
(the current heap) has been _commited_; at least on any JVM I've ever seen
the guts of.
You are correct that it is not allocated from the same heap.
The problem is that it is an allocation of resources that isn't accounted
for when deciding to garbage collect. (Have you ever seen a linux
box come to it's knees just because X is using >100MB and your out of swap?)
This is memory that is free'd when the Image object is gc'd, but if your
java application it's using much memory allocated from it's heap, then
the Image objects will never be gc'd.
Oh, I'm sorry... that's my bad. Hopefully this email will be plain text.
p.s. [OT] I sure wish people would stop posting this "text/alternate"
<x-html> stuff in public places... can a list serve be set to strip
that tripe out I wonder?
-- ---------------------- Rob Clark Dot Wireless, Inc. (858)552-2946 [EMAIL PROTECTED] ----------------------
