Re: WOWorkerThread deadlocks
Re: WOWorkerThread deadlocks
- Subject: Re: WOWorkerThread deadlocks
- From: Susanne Schneider <email@hidden>
- Date: Thu, 13 Sep 2012 17:57:28 +0200
Hi all,
please allow me to add one question regarding this interesting topic.
Alexis Tual (my mail client has problem with correct quoting) has
suggested for EOF background handling:
<snip>
ec.lock();
try {
// huge loop to compute stats
for (i = 0; i < 1000000; i++) {
// doing stuff with ec...
// cycling the ec
if (i % 100 == 0) {
ec.unlock();
ec.dispose();
ec = newEditingContextForMyWork();
ec.lock();
}
}
} finally {
ec.unlock();
}
</snip>
Now my question: is it correct to dispose the ec after unlock or would
it be better to do this beforehand, like:
ec.dipsose();
ec.unlock();
If I turn on the ec-lock logging in my application, there are many
remarks from the Finalizers like: "*** EOEditingContext: access with no
lock: _eoForGID()!" Is this a real problem or can it be ignored?
Best regards,
Susanne
--
Susanne Schneider
Coordinator secuTrial Development
iAS interActive Systems GmbH
Dieffenbachstraße 33 c, 10967 Berlin
fon +49 30 22 50 50 - 498
fax +49 30 22 50 50 - 451
mail email@hidden
web http://www.interActive-Systems.de
----------------------------------------------------
Geschäftsführer: Dr. Marko Reschke, Thomas Fritzsche
Sitz der Gesellschaft: Berlin
Amtsgericht Berlin Charlottenburg, HRB 106103B
----------------------------------------------------
_______________________________________________
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