Re: Diagnosing memory problems

> On Nov 27, 2018, at 16:56, Casey McDermott wrote: > > Our main window has a tool bar across the top, an outline view on the left, > and a tab view on the right. Choosing an item from the outline view fills a > data entry screen into a new tab on the right. > > We started out using OS 10.11

Re: Diagnosing memory problems

On Tue, 27 Nov 2018 16:53:26 -0700, Rob Petrovec said: >Actually, you want the Zombies tool. That finds overreleased objects >like ones that cause the spew you are seeing. See also: 1) man guardmalloc 2) 3) NSZombieEnabled 4) CFZombieLevel

Re: Diagnosing memory problems

Actually, you want the Zombies tool. That finds overreleased objects like ones that cause the spew you are seeing. —Rob > On Nov 27, 2018, at 4:52 PM, Rob Petrovec wrote: > > Check out the Leaks tool in Instruments (inside Xcode.app) > > —Rob > > >> On Nov 27, 2018, at 3:56 PM, Casey McDe

Re: Diagnosing memory problems

Check out the Leaks tool in Instruments (inside Xcode.app) —Rob > On Nov 27, 2018, at 3:56 PM, Casey McDermott wrote: > > Our main window has a tool bar across the top, an outline view on the left, > and a tab view on the right. Choosing an item from the outline view fills a > data entry sc

Diagnosing memory problems

Our main window has a tool bar across the top, an outline view on the left, and a tab view on the right.  Choosing an item from the outline view fills a data entry screen into a new tab on the right. We started out using OS 10.11, but just switched to newer OS versions.  10.12 has a couple dis

Re: Cocoa Newbie Thread/Memory Problems

I found the problem and it works! I had an extra: self.mXMLSourceData = nil; statement! I am now wondering if all my alloc/release calls are ok! Thanks again, All the Best Dave ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do no

Re: Cocoa Newbie Thread/Memory Problems

Hi Quincy, Sorry for the typeos and lack of clarity in my last message and thanks a lot for your help. I was really tired when I sent the message last night, I should have waited until today to send it. Basically what I was trying to get at is that I have a handler that gets called after

Re: Cocoa Newbie Thread/Memory Problems

On Mar 16, 2010, at 4:38 PM, Dave wrote: > - (NSString*)makeURLString:(NString*) theBaseURL ForDate:(NSDate*)theDate > UsingDatabse:(NString*) theDatabaseType Dave, Does it matter that UsingDatabse is misspelled ? Good Luck, Bill Hernandez Plano, Texas___

Re: Cocoa Newbie Thread/Memory Problems

On Mar 16, 2010, at 14:38, Dave wrote: > myURLString = [self myURLString:kBaseURL > ForDate:myCurrentDate UsingDatabase:@"rs_main"]; Do you mean 'self makeURLString:', the method whose implementation you showed? > [mParserBase myURLString ForStructure

Re: Cocoa Newbie Thread/Memory Problems

Hi Quincey, I added a call is NSLog() after each of the string assignment and it seems to work! At least I get sensible values for the fields. However, there still seems to be a problem. I need to make several URL calls when the button is clicked, so I changed the top-level button handler

Re: Cocoa Newbie Thread/Memory Problems

On Mar 16, 2010, at 09:57, Dave wrote: > At present I am not doing anything with the result, except assigning the > values so I can look at them in the debugger. The problem is that when I look > at the items in the array passed to the view controller the data retrieved is > not as it should be

Cocoa Newbie Thread/Memory Problems

Hi All, I adapted the sample code of "XMLPerformance" as a basis to start my own app. This is for the iPhone but I think it's a general problem with my understanding of Cocoa Memory Management and/or Threading. Basically I have a VewController with a button on it and when the user clicks

Re: Memory Problems

On Feb 5, 2010, at 5:49 PM, Greg Robertson wrote: > I am trying to parse a large CSV (5MB) file using some code I found here: > http://www.macresearch.org/cocoa-scientists-part-xxvi-parsing-csv-data > > but I am getting what I think is an out of memory error part way through, the > error is: >

Re: Memory Problems

On Feb 5, 2010, at 5:49 PM, Greg Robertson wrote: > I'm fairly certain I do not have a memory leak it is just that the NSString > is very large. Is there anyway to increase the memory allocated or clean up > the code to reduce its memory usage? Use an NSAutoreleasePool (check the docs) inside

Memory Problems

I am trying to parse a large CSV (5MB) file using some code I found here: http://www.macresearch.org/cocoa-scientists-part-xxvi-parsing-csv-data but I am getting what I think is an out of memory error part way through, the error is: DataImport(1324,0xa09f3500) malloc: *** mmap(size=16777216) fai