Re: locking problem
Re: locking problem
- Subject: Re: locking problem
- From: Ben Trumbull <email@hidden>
- Date: Sun, 19 Dec 2004 13:48:59 -0800
At 11:28 -0500 12/19/04, Nathan Dumar wrote:
To answer my own question here, after testing on my dev machine,
reset() causes some strange error if I try to use the EC again (even
if I also do ec = new EOEditingContext before using it). See end of
message for the error, for the morbidly curious.
It really looks like you still have a reference an EO that used to be
in the EC after calling reset.
Trying to reuse an EO after calling reset() or doing anything at all
with an EC or any of its ex-EOs after calling dispose() is very very
very BAD.
Keeping EOs around means there is still a hard reference to your EC.
So your ECs won't get garbage collected, so your app will leak a lot
of memory.
If edits in other ECs don't show up until you've disposed a different
EC, then you're doing something significantly wrong.
It might be best to step back from the dispose issue and explain the
higher level problem.
--
-Ben
_______________________________________________
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