Re: NSLock errors with Aperture 1.5.6

Subject: Re: NSLock errors with Aperture 1.5.6

From: Fraser Speirs <email@hidden>

Date: Wed, 20 Feb 2008 16:51:55 +0000

Delivered-to: email@hidden

On Mac OS X, messages to nil have no effect, so if the lock was nil the -unlock message would not be sent to an actual object.

My understanding of the "(null)" in the log message is that, in 10.5, NSLock objects can be named via -setName. In Aperture, such is not written for Leopard, the locks will not have names. The null, I'm guessing, comes from the fact that NSLock's -description method in 10.5 includes the name of the lock, which is nil for Tiger-compatible apps.

Best,

Fraser

---

http://speirs.org

http://connectedflow.com

http://flickr.com/photos/fraserspeirs

On 20 Feb 2008, at 02:01, Steve Weller <email@hidden> wrote:

I would guess that you failed to create the NSLock object and so it is null.

On Feb 19, 2008, at 11:49 AM, Juan Leon wrote:

Hi folks,

I am updating my plugin and found that I am getting a couple of NSLock errors that look like this in my plugin right after I call [_exportManager shouldBeginExport];
That I don't recall getting before.

I've carefully checked all of my progress sheet updates and all of them look like this:
[self lockProgress];
exportProgress.totalValue = [_exportManager imageCount];
exportProgress.currentValue = 1;
exportProgress.indeterminateProgress = NO;
exportProgress.message = @"Step 1 of 2: Preparing Images...";
[self unlockProgress];
[_exportManager shouldBeginExport];

The first error happens right after the above code in - (void)exportManagerShouldBeginExport

2/19/08 1:19:38 PM Aperture[8376] *** -[NSConditionLock unlockWithCondition:]: lock (<NSConditionLock: 0x1be9d660> '(null)') unlocked when not locked

I just built the sample plugin and got the same error. Should I be concerned? I haven't yet downloaded the 2.0 trial to test if it happens there too.

In addition, I also get this, in -exportManagerDidFinishExport *before* the -dealloc calls:

2008-02-19 14:39:28.388 Aperture[8882:e77b] *** -[NSConditionLock dealloc]: lock (<NSConditionLock: 0x1daa90c0> '(null)') deallocated while still in use
2008-02-19 14:39:28.394 Aperture[8882:e77b] *** Break on _NSLockError() to debug.

Greatful for any feedback!
Juan Leon
notoptimal.net

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Aperture-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/aperture-dev/email@hidden

This email sent to email@hidden

--
Blog: http://www.bagelturf.com/ Photos: http://bagelturf.smugmug.com/

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Aperture-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/aperture-dev/email@hidden

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Aperture-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/aperture-dev/email@hidden This email sent to email@hidden

References:
	>NSLock errors with Aperture 1.5.6 (From: "Juan Leon" <email@hidden>)
	>Re: NSLock errors with Aperture 1.5.6 (From: Steve Weller <email@hidden>)