I think I face the same bug but at another place.In some use-cases of my app, I need to call :NSOperation *nsOp = [featureLayer addFeatures:graphics]
When I call this immediately after map creation, I end up (not always, but VERY often) with an EXC_BAD_ACCESS. When I call this after a while, I generally have an operation which is never executed.I think there are some problems with operation queueing... But since I am not queuing the operation myself (it is internally queued by the "addFeatures" call and it returns the queued NSOperation), I cannot use your workaround.I tried to add an Objective-C category on AGSRequestOperation so that sharedOperationQueue returns one of my own allocated operation queue. For now it seems to work. But note that it seems not to work with a static variable, don't know why. @implementation AGSRequestOperation (Operation)
+ (NSOperationQueue *)sharedOperationQueue {
return [Utils getQueue];
}
@endAnd the Utils code :
// Declaration in .h file
@property (nonatomic,strong) NSOperationQueue *operationQueue;
@implementation Utils
- (id)init
{
self = [super init];
if (self) {
_operationQueue = [[NSOperationQueue alloc] init];
[_operationQueue setMaxConcurrentOperationCount:10];
}
return self;
}
+ (NSOperationQueue *)getQueue {
return _operationQueue;
}
@endActually, I don't really know what arcgis does internally to schedule this task. All I know is that there is something not good regarding object allocation / retain thing.I need some more tests to make sure that it works ALL the time. That would be great to have inputs from an ArcGis guy and to investigate on a fix.Christophe.
