FROM : Scott Ribe
DATE : Sat Jan 05 01:34:10 2008
And I forgot the most important point. I believe that NS image classes do
some caching of images for performance, behind your back, out of your
control. It's possible that accounts for the perceived leak that you saw,
and that if you use your initial method to process a large number of images,
the cache will get flushed before the "leak" grows too large.
Of course it's also possible there's a bug: in your code with
retain/release, or no autorelease pool in a thread; or less likely in Cocoa
functions.
--
Scott Ribe
<email_removed>
http://www.killerbytes.com/
(303) 722-0567 voice
DATE : Sat Jan 05 01:34:10 2008
And I forgot the most important point. I believe that NS image classes do
some caching of images for performance, behind your back, out of your
control. It's possible that accounts for the perceived leak that you saw,
and that if you use your initial method to process a large number of images,
the cache will get flushed before the "leak" grows too large.
Of course it's also possible there's a bug: in your code with
retain/release, or no autorelease pool in a thread; or less likely in Cocoa
functions.
--
Scott Ribe
<email_removed>
http://www.killerbytes.com/
(303) 722-0567 voice
| Related mails | Author | Date |
|---|---|---|
| Adam Knight | Jan 4, 23:25 | |
| Adam Knight | Jan 5, 00:45 | |
| John Stiles | Jan 5, 00:51 | |
| Chris Williams | Jan 5, 01:19 | |
| Scott Ribe | Jan 5, 01:30 | |
| Scott Ribe | Jan 5, 01:34 | |
| Shawn Erickson | Jan 5, 01:56 | |
| Adam Knight | Jan 7, 18:41 |






Cocoa mail archive

