Re: ARC Retain Cycles
Re: ARC Retain Cycles
- Subject: Re: ARC Retain Cycles
- From: Alex Kac <email@hidden>
- Date: Sat, 26 Apr 2014 12:06:40 -0600
At least for me, I do think in terms of how autorelease works. Its second nature. The moment I see a loop of any kind, I think about a temporary pool of objects and if I should do something about it. I just simply have no issues with autorelease and think of it as a great feature that I use with or without ARC.
You’re a programmer - you’re supposed to know what happens under the hood. That’s part and parcel of developing good, optimized software.
On Apr 26, 2014, at 11:32 AM, Dave <email@hidden> wrote:
> If the OS didn’t allocate autoreleased objects there wouldn’t be a problem at all, it does though so it becomes neccessary to have to worry about cleaning up after the OS.! You can twist the language any way you like, but the problem is autorelease, not anything else.
>
> Autorelease is really the pits IMO, use it at your peril, it’s just a shame the OS pollutes an otherwise well *managed* memory scheme.
>
> Before I converted to ARC and merged in some code, it worked without any drains and didn’t use 150 MB. The introduction or side effect autorelease behind the scenes caused an otherwise fine loop into a memory hogger. Using auto release caused me to have to profile the app carefully and find the problem. This probably took 1 to 1.5 days to do, if the OS didn’t use autorelease, I wouldn’t have had to spend that time finding and cleaning up after the OS!
>
> Really, what OS other, makes you clean up after it?
Alex Kac - President and Founder
Web Information Solutions, Inc.
My wife and I do a lot of things together including Halo 3 and firearm training. She's awesome.
_______________________________________________
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