Re: NSTableView and memory management problem.
Re: NSTableView and memory management problem.
- Subject: Re: NSTableView and memory management problem.
- From: Matt Neuburg <email@hidden>
- Date: Mon, 28 Mar 2005 10:40:38 -0800
On Mon, 28 Mar 2005 00:18:58 +0200, marko68 GMX <email@hidden> said:
>Hello,
>Seems I need an expert advice on memory management issue. I wrote a
>Data Viewer, able to display some data of auxiliary structure. And
>everything works fine until I load really huge datasets. The used
>scheme is trivial - I have the main array, keeping additional arrays
>(rows), allocating for every row its personal array, containing NCell
>objects, initialized with data during the reading stage. But what
>happens when I try to operate with huge data? Let's say a table,
>having 2020 variables and 1975 rows. When such a table is loaded, the
>Data Viewer consumes about 200 MB of the memory. When user closes the
>Data Viewer window (but not the application itself, the application
>has some additional forms to be displayed), I clean up the mentioned
>arrays (retainCount of all object is 0, they are really ready to be
>destroyed) and expect to see that all used memory is returned to the
>OS (I use Activity Monitor to check it). But it does not happen. I
>tried to use NSAutoreleasePool but it did not help.
Use ObjectAlloc, not Activity Monitor (as I've said three times in the last
week, it seems). That is the only way to pierce the veil of virtual memory
and see whether *you* are actually leaking memory. If you are not, then just
don't worry about it. m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide
<http://www.amazon.com/exec/obidos/ASIN/0596005571/somethingsbymatt>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden