>>
Date: Sunday, 22 June 2014 5:24 am
To: Kyle Sluder mailto:k...@ksluder.com>>
Cc: Development
mailto:varun.chandramo...@wontok.com>>,
Cocoa-Dev List mailto:Cocoa-dev@lists.apple.com>>
Subject: Re: NSReleasePool issue
On Jun 21, 2014, at 11:16 AM, Kyle Sluder
mailto:
On 23 Jun 2014, at 01:00, Varun Chandramohan
wrote:
> I agree on the fact that if the auto pool is introduced in main then its
> going to mask all the leaks in other parts of the code leading to unknown
> memory leaks. I see a divided option on this, but in OSX world this should be
> taken car
t mailto:Cocoa-dev@lists.apple.com>>
Subject: Re: NSReleasePool issue
On Jun 21, 2014, at 11:16 AM, Kyle Sluder
mailto:k...@ksluder.com>> wrote:
The pool will never be drained, because NSApplicationMain never returns. There
is no wasted work here.
But it's still true that any ob
On 21 Jun 2014, at 22:01, Scott Ribe wrote:
> On Jun 21, 2014, at 12:16 PM, Kyle Sluder wrote:
>
>> And as far as I can remember, developers have _always_ been responsible for
>> setting up a backstop autoreleasepool.
>
> Never.
On Mac, Scott is right. On iOS, this seems to be what Apple’s d
On Jun 21, 2014, at 12:16 PM, Kyle Sluder wrote:
> And as far as I can remember, developers have _always_ been responsible for
> setting up a backstop autoreleasepool.
Never.
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
_
On Jun 21, 2014, at 11:16 AM, Kyle Sluder wrote:
> The pool will never be drained, because NSApplicationMain never returns.
> There is no wasted work here.
But it’s still true that any object autoreleased into that pool is effectively
leaked. It just won’t be visible as such to the ‘leaks’ to
> On Jun 21, 2014, at 10:25 AM, Jens Alfke wrote:
>
>
>> On Jun 21, 2014, at 7:39 AM, Kyle Sluder wrote:
>>
>> You should add the @autoreleasepool around NSApplicationMain. I don't know
>> why it's missing from the Mac template.
>
> I disagree. It’s pointless to have an autorelease pool that
> On Jun 21, 2014, at 10:25 AM, Jens Alfke wrote:
>
> On Jun 21, 2014, at 7:39 AM, Kyle Sluder wrote:
>
>> You should add the @autoreleasepool around NSApplicationMain. I don't know
>> why it's missing from the Mac template.
>
> I disagree. It’s pointless to have an autorelease pool that won
On Jun 21, 2014, at 7:39 AM, Kyle Sluder wrote:
> You should add the @autoreleasepool around NSApplicationMain. I don't know
> why it's missing from the Mac template.
I disagree. It’s pointless to have an autorelease pool that won’t be drained
till the application quits. Anything autoreleased
gt; autoreleasepool.
>
> From: Sean McBride
> Sent: Saturday, June 21, 2014 2:39 AM
> To: Steve Christensen; Varun Chandramohan
> Cc: Cocoa-Dev List
> Subject: Re: NSReleasePool issue
>
> Given the backtrace, I'd say the OP is using Mac
This is OS X not iOS. Yes main look like what is shown below without the
autoreleasepool.
From: Sean McBride
Sent: Saturday, June 21, 2014 2:39 AM
To: Steve Christensen; Varun Chandramohan
Cc: Cocoa-Dev List
Subject: Re: NSReleasePool issue
Given the
Given the backtrace, I'd say the OP is using Mac OS, not iOS. I just created a
new project in Xcode, and main() looks like this on OS X:
int main(int argc, const char * argv[])
{
return NSApplicationMain(argc, argv);
}
On Fri, 20 Jun 2014 09:32:48 -0700, Steve Christensen said:
>My ma
My main() looks like this. Does yours specify an autorelease pool?
int main(int argc, char* argv[])
{
@autoreleasepool
{
return UIApplicationMain(argc, argv, nil,
@"MyDelegateClassName");
}
}
On Jun 19, 2014, at 5:45 PM, Varun Chandramohan
wrote:
> I w
13 matches
Mail list logo
