On Tue, 19 Oct 2010 10:33:39 +0700, Gerriet M. Denkmann said:
>So, what to do now?
>Conclude that AppKit is full of leaks?
AppKit is full of leaks, just like most all real world code. Create a
new document-based Cocoa app from Xcode stationary, run it, open the
about box, open panel, save panel,
On Oct 18, 2010, at 8:33 PM, Gerriet M. Denkmann wrote:
> First of all: Thank you very much for this very helpful article.
>
> I just created a new Cocoa Document based app in Xcode (Version 3.2.4).
> I did not edit any of the Xcode supplied files.
> Clicked Build and then Run with Performance T
On 18 Oct 2010, at 19:56, Bill Bumgarner wrote:
> I wrote up an article on how to use the "Mark Heap" / "Heapshot
> Analysis" tools in Instruments to detect, analyze, and fix memory leaks,
> including those that leaks can't find.
>
>
> http://www.friday.com/bbum/2010/10/17/when-i
On Oct 18, 2010, at 8:42 AM, Matt Gough wrote:
> Perhaps Apple should aim Instruments at itself. Inspired by Bill's post, I
> just did a HeapShot test on my own app. Instruments went up to 2.5GB real Mem
> and stayed at that when I closed the Instrument window.
"2.5GB Real Mem" is relatively m
To my Cocoa Keepers file.
Bill thank you very much, I didn't know what Heapshot did and what the output
meant. Now I do.
On 18-Oct-2010, at 11:52 AM, Bill Bumgarner wrote:
> Folks--
>
> I wrote up an article on how to use the "Mark Heap" / "Heapshot
> Analysis" tools in Instruments
Folks--
I wrote up an article on how to use the "Mark Heap" / "Heapshot
Analysis" tools in Instruments to detect, analyze, and fix memory leaks,
including those that leaks can't find.
http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-fin
