FROM : Jens Alfke
DATE : Mon Jun 16 17:51:22 2008
There's nothing inherently strange about this leak. Just because an
object was created down inside the Cocoa frameworks doesn't mean that
they're responsible for it being leaked. Anything that retains the
object might be responsible, if it forgets to release it. You have to
consider all the code that accesses this object.
Either some code you aren't showing is retaining that NSData object
(possibly the udpGetIp: or udpGetPort: methods), or your code is
running on a background thread that doesn't have an autorelease pool.
In the latter case you'd already be getting warnings about objects
being leaked, though.
—Jens
DATE : Mon Jun 16 17:51:22 2008
There's nothing inherently strange about this leak. Just because an
object was created down inside the Cocoa frameworks doesn't mean that
they're responsible for it being leaked. Anything that retains the
object might be responsible, if it forgets to release it. You have to
consider all the code that accesses this object.
Either some code you aren't showing is retaining that NSData object
(possibly the udpGetIp: or udpGetPort: methods), or your code is
running on a background thread that doesn't have an autorelease pool.
In the latter case you'd already be getting warnings about objects
being leaked, though.
—Jens
| Related mails | Author | Date |
|---|---|---|
| Aarno Syvänen | Jun 16, 12:08 | |
| Igor Mozolevsky | Jun 16, 12:57 | |
| Jens Alfke | Jun 16, 17:51 | |
| Hamish Allan | Jun 16, 21:14 | |
| Jens Alfke | Jun 17, 04:32 |






Cocoa mail archive

