Stop NSXMLParser Instance from Causing _NSAutoreleaseNoPool

Posted by PF1 on Stack Overflow See other posts from Stack Overflow or by PF1
Published on 2010-05-22T19:35:03Z Indexed on 2010/05/22 19:40 UTC
Read the original article Hit count: 195

Filed under:
|
|
|
|

Hi Everyone:

In my iPhone application, I have an instance of NSXMLParser that is set to a custom delegate to read the XML. This is then moved into its own thread so it can update the data in the background. However, ever since I have done this, it has been giving me a lot of _NSAutoreleaseNoPool warnings in the console. I have tried to add a NSAutoreleasePool to each of my delegate classes, however, this hasn't seemed to solve the problem. I have included my method of creating the NSXMLParser in case that is at fault.

NSURL *url = [[NSURL alloc] initWithString:@"http://www.mywebsite.com/xmlsource.xml"];
NSXMLParser *xmlParser = [[NSXMLParser alloc] initWithContentsOfURL:url];

CustomXMLParser *parser = [[CustomXMLParser alloc] init];

parser.managedObjectContext = self.managedObjectContext;

parser = [parser initXMLParser];

[xmlParser setDelegate:parser];

[NSThread detachNewThreadSelector:@selector(parse) toTarget:xmlParser withObject:nil];

If anyone has any ideas to get rid of this problem, I would really appreciate it.

Thanks.

© Stack Overflow or respective owner

Related posts about iphone

Related posts about Xml