On Thu, Jun 5, 2008 at 9:47 AM, Graham Cox [EMAIL PROTECTED] wrote:
In my app I'm getting a hang when my main document window is asked to
close. This occurs only if there are unsaved changes, but it hangs before
the unsaved changes sheet is presented.
If I link against the 10.4u SDK (but
OK, this is really weird, and frustratingly difficult to get a grip on.
By preventing certain things initialising in my app, I can get sheets
to work. So I'm quite prepared to agree that it's something I'm doing
that is causing some subtle corruption somewhere that just happens to
throw a
If there were a Dr. House for debugging, this is the kind of
diagnostic challenge he'd like.
Stab in the dark: you mentioned that you're on 10.5.3. Do you have a
10.5.2 machine you can use to see if the hang still occurs? Maybe
it's not a Tiger/Leopard thing but a 10.5.2/10.5.3 thing.
In my app I'm getting a hang when my main document window is asked to
close. This occurs only if there are unsaved changes, but it hangs
before the unsaved changes sheet is presented.
If I link against the 10.4u SDK (but still run on 10.5), this does not
occur, but if I link against the
On Jun 4, 2008, at 9:17 PM, Graham Cox wrote:
Where should I start to look to debug/fix this? I just can't see
where I need to set a breakpoint to begin with.
Run your app in the debugger. When it hangs, hit the pause button in
the debugger and take a look at the backtrace in the thread
You can use the Spin Control application (/Developer/Applications/
Performance Tools/Spin Control.app) to start... that will let you know
what's going on when it starts to hang (this application profiles
everything, so just start it before you launch your application,
launch your app and
Thanks for the tip - easy!
I wish the bug was that easy here's my stack trace. Looks like the
hang is in actually trying to display the save changes sheet itself,
rather than any particular logic problem, which is what I was assuming
was going on. So, I tried some other sheets I have
