Re: crashing in Objective-C Cocoa code in Carbon app under Leopard
Re: crashing in Objective-C Cocoa code in Carbon app under Leopard
- Subject: Re: crashing in Objective-C Cocoa code in Carbon app under Leopard
- From: email@hidden
- Date: Tue, 22 Jan 2008 20:30:25 -0600
- Priority: normal
> If you ever show file-save/open dialogs or print things, your code is
> using lots of Cocoa :)
Yes, I can understand that there are parts of the OS that would be using Cocoa, but I do not understand why the message dispatcher would be calling into Cocoa when there are only Carbon windows visible and there are no file dialogs open at the time of the crash.
> Try turning on NSZombieEnabled; that may prove to be enlightening. There
> are definitely cases where bad memory usages (e.g. double frees) might
> have not caused problems in one OS but will cause problems in another.
Thanks, I will try this.
I have been using the ObjectAlloc tool and have noticed that there are negative numbers of a "GeneralBlock--16" object (note that this is different from a "GeneralBlock-16" object) and that that number increases (in the negative direction) whenever a File Save dialog is opened or closed. Unfortunately, ObjectAlloc does not save the stack trace for these allocations so I cannot tell how they are being created(?).
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden