I noticed something interesting the other day, which I think would qualify as a memory leak.

Example:  create an java.awt.Image instance... the some/most of the memory for the image is allocated under the X server process, but the VM does not take this memory into account when deciding whether to garbage collect.  The result is that if you get rid of references to an Image, the memory under the X server process isn't freed until the Image object is gc'd, which doesn't happen because the VM is under it's threshold to begin garbage collection.  The solution, I think, would be to keep track of memory used by XImage's, and count that towards the threshold used to begin garbage-collection.
 
 
 

-- 
----------------------
Rob Clark
Dot Wireless, Inc.
(858)552-2946
[EMAIL PROTECTED]
----------------------
 


Reply via email to