Getting memory leak in NSXMLParser

Question

Im getting the same memory leak as I mentioned the link below.

NSXMLParser Leaking.

Is it the real problem from the Apple developing side?

And in that link I saw the answer from Lee Armstrong as:

Apple have got back to me and this is a bug #6469143

Looks like they plan to fix for 4.0

Is there any documentation regarding to this problem???

Anyone's help will be much appreciated.

Thank you, Monish.

Hello guys,I need a quick answer from you.I am waiting for your suggestions. — monish, Mar 19 '10 at 12:08

score 1 · Accepted Answer · edited May 23 '17 at 12:19

1

According to the thread you linked to, Apple has acknowledged this as a bug and it will be fixed in a forthcoming release of the iPhone OS. So it looks like you're out of luck until then. There is no documentation as to what's actually getting leaked, because the leak is inside Apple's code and we (obviously) don't have ready access to Apple's source code.

edited May 23 '17 at 12:19

Community

1
1

answered Mar 19 '10 at 14:12

Dave DeLong

242,470
58
448
498

Thanks for your information.Does the leaks may leads to Application crash or any Exceptions?? – monish Mar 20 '10 at 04:55
can any one gimme reply for my question I posted as comment. – monish Mar 20 '10 at 09:01
Leaking memory will not generate any exceptions, but it might generate a crash if you leak enough memory (many megabytes worth) to run out of heap space. This `NSXMLParser` leak is unlikely to do that (unless you're creating thousands and thousands of `NSXMLParser` objects) – Dave DeLong Mar 20 '10 at 16:01

score 0 · Answer 2 · answered Jan 29 '11 at 08:13

0

NSXMLParser will leak if the URL you provided is not valid.

answered Jan 29 '11 at 08:13

Robert Neagu

498
4
11

Seems to always leak with URL. Workaround: http://stackoverflow.com/questions/6019240/memory-leak-using-nsxmlparser-in-nsconcretemaptable – SwiftArchitect Mar 21 '12 at 18:30

Getting memory leak in NSXMLParser

2 Answers2