Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Class gets EXC_BAD_ACCESS only as NSOperation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Class gets EXC_BAD_ACCESS only as NSOperation

Subject: Class gets EXC_BAD_ACCESS only as NSOperation
From: James Maxwell <email@hidden>
Date: Tue, 24 Mar 2009 07:33:13 -0700

I have a method that I want to run in the background. When I run it in the app's main thread, all's well, but when I run it as an NSOperation I get an EXC_BAD_ACCESS error. The error happens when trying to initialize a local float array.

I know bad access errors are usually caused by trying to access a pointer that's already been released, but if that were the case here, wouldn't it do the same when running in the main thread?

Are there any obvious things I should check in how I'm creating the NSOperation?

btw, I'm using NSOperationQueue to fire the operation.

J.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: Class gets EXC_BAD_ACCESS only as NSOperation
From: Bill Bumgarner <email@hidden>


Prev by Date:
Re: Trouble with NSAnimationContext

Next by Date:
Re: iPhone Tab bar Question

Previous by thread:
Re: Using NSValueTransformer to convert NSImage to NSData

Next by thread:
Re: Class gets EXC_BAD_ACCESS only as NSOperation

Index(es):

Date
Thread