Re: How to track down this memory problem?
Re: How to track down this memory problem?
- Subject: Re: How to track down this memory problem?
- From: Adam Knight <email@hidden>
- Date: Sat, 22 Jul 2006 14:05:17 -0500
Well, I reduced it to 100% Apple's code (that is, a stock Core Data
Document-based project, my model, and some bindings). So I think
that's pretty definitive and I'll file a bug on it.
For the interested, nab the following, build it, and open the
included file. Then just click on a different entry in the list and
use the arrow keys to go up an down the list until it breaks.
http://www.codepoetry.net/files/NotaeTestCase.zip
--
Adam Knight
If you're not going to stop and appreciate the scenery, you're not
going to
enjoy Myst. The same thing applies on the Mac as well. -- Rand Miller
On Jul 22, 2006, at 2:58 AM, Andy Lee wrote:
On Jul 22, 2006, at 2:06 AM, Adam Knight wrote:
I've commented all my observing code out, all my major functions,
disabled all features, etc. and the bug stands no matter how much
I remove. It's reduced sometimes, but never eliminated.
This is a good start -- trying to narrow the problem down to the
root cause by process of elimination. I would suggest going even
further. Try to create the smallest possible "Hello, world"
application that reproduces the problem. Then send it to Apple, or
post it here.
--Andy
_______________________________________________
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
_______________________________________________
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