As requested, here a small runnable test. When you run it please start the JVM
with something like -XX:NewSize=256m -XX:MaxNewSize=256m, elsehow the memory
message wont be of much use.
Here comes the code:
I am not sure what is going on. Perhaps this Runtime reporting wrong values.
I see that number printed to the console is growing but at the same time
i do not observe heap growth in the jconsole.
-igor
[EMAIL PROTECTED] wrote:
As requested, here a small runnable test. When you run it
Hello Igor,
thank you for your reply. Its not only the runtime the reporting: in the
original application where I extracted this code from, it produced a noticable
slowdown in the rendering threads because of the garbage collector runs.
As I said, since I am using MemoryImageSources now, it
Hmm, the forum is cropping my code. Is it to long? Do I need to use some tag
like [pre]? I will try to edit the post
[Message sent by forum member 'chaose71' (chaose71)]
http://forums.java.net/jive/thread.jspa?messageID=269280
I only see a bunch of small collections (I tried on
6u10) - probably because for each pixel you set an
int[1] array is created.
I don't see the heap growing. Run it with -verbose:gc ,
see what it says.
If you want to try the approach Clemens suggested, you'll
only need to change
