Re: Losing my memory - a caching problem?
Re: Losing my memory - a caching problem?
- Subject: Re: Losing my memory - a caching problem?
- From: "Sean McBride" <email@hidden>
- Date: Wed, 18 Aug 2010 10:57:02 -0400
- Organization: Rogue Research Inc.
On Tue, 17 Aug 2010 23:00:02 +0100, Stuart Rogers said:
>>>> Have you tried using drain instead of release? That seems to be the
>>> preferred way at this point, triggering GC collection if needed (I don't
>>> know if your code is GC enabled, but if the library code is GC enabled,
>>> then this will solve some of those problems)
>>>
>>> My app is uses retain/release - I have an aversion to garbage
>collection - so
>>> (according to the documentation) drain will do exactly the same as
release.
>>
>> Still, using drain is probably a good habit to get into. For example,
>> the clang static analyzer flags using release on an autorelease pool as
>> a warning.
>
>Really? For me, after a clean build, Build & Analyse doesn't complain.
>What warning do you get?
Perhaps you have to be building as GC... it says:
"Use -drain instead of -release when using NSAutoreleasePool and garbage
collection"
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden