• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSXMLNode's `stringValue' method and memory leaks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSXMLNode's `stringValue' method and memory leaks


  • Subject: NSXMLNode's `stringValue' method and memory leaks
  • From: Damien Sorresso <email@hidden>
  • Date: Fri, 2 Dec 2005 18:36:30 -0600

I'm using NSXMLNode's `stringValue' method to get the raw string value of an XML node, but it seems like every time I call this method, I get

2005-12-02 18:15:20.818 XMLTest[15637] *** _NSAutoreleaseNoPool(): Object 0x307ea0 of class NSCFString autoreleased with no pool in place - just leaking

in the run log. But from what I can tell, the object it returns isn't autoreleased. The assignment statement is

curVal = [[names objectAtIndex:i] stringValue];

The `names' array contains `NSXMLNode' objects, and it is obtained from a `NSXMLNode' passed into the function. Every time the above statement is executed, the aforementioned message is printed to the console. The address of the object in the message is always the same as the address of `curVal'.

What's going on here?
--

Damien Sorresso

"If English was good enough for Jesus Christ, then it is good enough for Texas children."
-Texas Governor "Ma" Ferguson, holding a King James Bible in her hand, on Spanish being taught in Texas public schools.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Follow-Ups:
    • Re: NSXMLNode's `stringValue' method and memory leaks
      • From: Glen Simmons <email@hidden>
    • Re: NSXMLNode's `stringValue' method and memory leaks
      • From: j o a r <email@hidden>
  • Prev by Date: Re: Is Apple's singleton sample code correct?
  • Next by Date: Re: NSXMLNode's `stringValue' method and memory leaks
  • Previous by thread: Reducer Tutorial leak?
  • Next by thread: Re: NSXMLNode's `stringValue' method and memory leaks
  • Index(es):
    • Date
    • Thread