Hi everybody,
I know this isn't the right place to ask my question, but it has a lot to do with the
discussed subject.
Justin Couch wrote:
> What I believe you are seeing is a function of extremely poor image
> loading that Sun provides as default with the JDK.
>
> The basic problem is this: If your image is 128x128 pixels at 4 bytes
> per pixel, this requires 65K of memory. Due to Sun's design, the Image
> object created as a result consumes just over 4 times this amount of
> memory (ie 262K) which is exactly four copies of the image plus a little
> for overheads. If you check the source, you will see that copies are
> kept all over the place in what is an _extremely_ messy and poor
> implementation.
I want to make an image with the "default JDK" createImage() function of 2400x2600
pls. With 4bpp it makes the picture nearly 25Mb. Is there any way to create the image
with less bytes per pixel. And is it true that this image is also kept four times in
memory, so the heap must be at least 100 Mb!! ?
I appreciate all suggestions.
Thanks in advance,
Patrick.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
