If you can reproduce this in a sample project with your model, you
should definitely file a bug. If you can attach your program and
steps to reproduce, you could file a bug with that as well.
I've filed Radar 6480291 with the app, user's data file, and
instructions.
For the archives, fol
Hi Ben,
Thanks for the response. I'm rearranging your email a bit to respond
to pertinent bits in one place:
The stack trace is:
5
4 CoreData -[_NSFaultingMutableSet objectEnumerator]
3 CoreData -[_NSFaultingMutableSet willRead]
2 CoreData -[NSManagedObjectContext(_NSInternalAdditi
p.s.
But when these are faulted in, according to Instruments, Core Data
allocates a GeneralBlock-528384 per record! Even if you naively
preallocated a good chunk of memory for the strings, I can't imagine
using more than 1-2KB per record, so 516KB is totally ridiculous.
When I run Instrument
We're running into a situation where Core Data is making very large
memory allocations when faulting in small amounts of data.
The entity has:
- 2x Date
- Int16
- 4x Int32
- Boolean
- String
- to-one relationship
- String (in a subentity)
- to-one relationship (in a subentity)
-
We're running into a situation where Core Data is making very large
memory allocations when faulting in small amounts of data.
The entity has:
- 2x Date
- Int16
- 4x Int32
- Boolean
- String
- to-one relationship
- String (in a subentity)
- to-one relationship (in a subentity)