Hi Rob Keniger, Joar and Nick Zitzmann,
Thanks for your quick replies and thanks in advance to anyone else who
replies.
Rob and Joar you were right about Guard Malloc. Its running perfectly
now. What a huge relief. I had visions of core data database format
incompatibilities...
Its probably w
On 08/11/2008, at 3:28 PM, Steve Steinitz wrote:
I have a Core Data application that worked well when built from Xcode
3.0. I updated to the iphone SDK version of Xcode 3.1 and now the app
no longer works. It won't open the production database but will
open a
small, testing database. When
On Nov 7, 2008, at 9:28 PM, Steve Steinitz wrote:
When the app starts up it gives the following
(not sure if its a problem, I've just never seen it before):
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMal
On Nov 7, 2008, at 10:28 PM, Steve Steinitz wrote:
When I attempt to load the large production database it uses a lot of
CPU for a while and then finally fails with this:
Attempt to allocate 4194304 bytes for NS/CFDictionary failed
1 _NSOutOfMemoryErrorHandler (in Foundation) + 72
Hello,
I have a Core Data application that worked well when built from Xcode
3.0. I updated to the iphone SDK version of Xcode 3.1 and now
the app
no longer works. It won't open the production database but will
open a
small, testing database. When the app starts up it gives the following
(n
