green
threads):
> > "AWT-Finalizer" (TID:0x404c55f8, sys_thread_t:0x8681d98,
state:CW)
> > prio=9
> > at java.lang.Object.wait(Native
Method)
> > at java.lang.Object.wait(Object.java:424)
> > at sun.awt.AWTFinalizer.run(AWTFinalizer.java:46)
> >
--
--
Rob Clark
Dot Wireless, Inc.
(858)552-2946
[EMAIL PROTECTED]
--
uld 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]
--
cated from it's heap, then
the Image objects will never be gc'd.
p.s. [OT] I sure wish people would stop posting this "text/alternate"
stuff in public places... can a list serve be set to strip
that tripe out I wonder?
Oh, I'm sorry... that's my bad. Hopefully this em
memory
allocated outside the JVM's heap (a wrapper for malloc() and free() would
be the way to go, for the legacy code example), a resource for x-server
resouces held, etc.)
--
--
Rob Clark
Dot Wireless, Inc.
(858)552-2946
[EMAIL PROTECTED]
--
"Daniel W. Dulitz x108" wrote:
> Rob Clark writes:
> > Here's a crazy idea: the whole problem, as I see it, arises because
> > the JVM's garbage collector only knows of one resource pool, the
> > heap, when in fact there are other resource pools outsid
