I wanted to clarify/correct what I had said earlier:
> I believe that, as of jdk 1.3 and later, all decoded images
> are stored as BufferedImage objects internally and are, therefore,
> stored on the Java heap. We are currently working on mechanisms
> in jdk 1.4 to cache some images in platform-specific representations
> (for example, as DirectDraw surfaces on win32); this would
> essentially get the decoded images out of the Java heap
> (but not necessarily onto the native heap, since they may actually
> be allocated in vram in some situations).
Caching the decoded images outside the Java heap (whether in
VRAM or elsewhere) would not necessarily remove the
representations of the images from the Java heap. There will
be some new mechanisms in jdk1.4 whereby images can be created
on the native platform -instead- of on the Java heap. But for
existing API such as the image decoders, there will still
be Java representations of the image that can be used as
backup for any existing cache. So the memory footprint
in Java does not necessarily change with these images, although
the underlying rendering details might.
Chet.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
