Back in JDK1.2 the Java native image libraries used to leak a lot of memory. The copy I worked for wrote their own JNI image libraries to
work around these problems.
I would have thought these issues would have been fixed by now, but
who knows.
regards Malcolm
From: "Adam Greene" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: [Tapestry-developer] Memory Leaks in JVM
Date: Thu, 23 Jan 2003 12:30:43 -0400
This is kind of off topic, but I was wondering if anyone has had problem
with JPEGEncoder / JPEGDecoder stuff. I have a file that I upload via a
Form, decode it, resize it, and then recompress it. When the operation is
completed, GC cannot release a lot of the memory allocated. I have done
everything I can find : dispose() unused images, close() unused streams
(especially ByteArrayOutput/InputStream), even called System.gc() after each
encoding operation. Sun says there is nothing wrong with the JPEG code, but
something is wrong.
Again, sorry for being off topic, but I couldn't think of anywheres else
that I could find people that understand Java.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
