What made the difference was having the Component class' "finalize
()" method explicitly call "flush()" on its BufferedImage before
nulling it out.
I hope this helps to shed some light on the situation.
All except for what the fix is indicated to be - at least as far as
my testing goes but that could be lacking some essential ingredient.
You might be in a situation where you are accumulating 1000's of the
48 byte chunks I originally started out freeing. But it would have to
be quite a few to be involved in OutOfMemory exceptions. Otherwise my
testing has shown flush() not making any kind of a difference as far
as BufferedImage goes.
With whatever test data you have a bug report might be in order if GC
is in fact broke with or without regard to the flush() method.
_______________________________________________
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
