Re: cross development problem
Re: cross development problem
- Subject: Re: cross development problem
- From: Thomas Bauer <email@hidden>
- Date: Tue, 18 Jul 2006 18:46:37 +0200
I hate to be a skeptic, but releaseExclusiveAccess sanity checks
itself against an internal reference count. Extraneous releases are
essentially just no-ops. The only way it would cause harm is if the
object upon which it was been invoked was invalid. Which makes me
wonder...
There was a "aquireExclusiveAccess" just before running the DRErase
via a DREraseProgressPanel
and an immediate releaseExclusiveAccess in the notification callback
after the erase. Maybe at this moment this causes a problem?
The code continued fine into a deviceStatusChanged callback (caused
by DRDevice going into transition) but crashed in some parallel
thread (belonging to the DRFramework I guess).
Do you ever release a DRDevice? Its unlikely you would have to,
since all the methods to get them from DR are get and not copy or
create. Releasing DRDevices out from under DR is a very common
mistake, and would cause this symptom.
No, I never release a DRDevice.
cheers
tom
-Ed
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden