Re: java.lang.outofmemory
Re: java.lang.outofmemory
- Subject: Re: java.lang.outofmemory
- From: Art Isbell <email@hidden>
- Date: Tue, 7 Mar 2006 13:11:12 -1000
On Mar 7, 2006, at 1:00 PM, Paul Lynch wrote:
On 7 Mar 2006, at 22:46, Jacky Gagnon wrote:
First, its not a good idea to use invalidateAllObjects() to free
memory; call saveChanges more frequently or just fetch what you
need.
saveChanges() doesn't release snapshots, unfortunately, which I
would surmise is the problem.
But if snapshot reference counting is working as advertised,
dereferencing the only editing context containing references to the
snapshots should release them.
it may also be acceptable to use dispose(),
dispose() should be invoked when an editing context is about to be
garbage-collected, so sending an explicit dispose() message seems
redundant.
but invalidateAllObjects(), and its variants, are the only way to
flush the snapshots.
Other than removing any references which doesn't involve the
invalidateAllObjects() overhead of converting all of the objects to
faults. So invoking invalidateAllObjects() seems like a waste to me.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden