Rob:
Good thoughts, but no threads other than the normal Java overhead, and
I'm doing one image at a time, extracting information from each and
storing that information in a heap-allocated regular Java data
structure.
Rob Lockstone <email@hidden> wrote:
> You say you're allocating a maximum 1500M java heap. But it looks like
> you're not even getting close to that figure from the Full GC info you
> provided. In fact, the java heap is actually jumping *down* in size,
> which is something I haven't seen before.
Fascinating, isn't it?
> But it would seem to
> indicate that it's attempting to give up java heap memory for other
> non-java-heap activities (most likely the image processing is my
> guess).
Um, what exactly is going on in Java image processing that takes lots of
memory (I've got 8GB or so of RAM unused when this happens) but doesn't
happen in the heap?
These are not big images -- they're 8-bit grayscale 300DPI 8.5x11 page
images. Now if I was doing 8000x8000 24-bit color, I could see some
issues...
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
