Re: App won't launch after a crash
On Oct 1, 2012, at 03:08 PM, Kyle Sluder wrote: > On Mon, Oct 1, 2012, at 07:20 AM, Mike Abdullah wrote: >> >> On 1 Oct 2012, at 13:13, Martin Hewitson >> wrote: >> >>> Oops, sorry, I chopped off the top of the report. Here it is: >>> >>> Exception Type: EXC_CRASH (SIGABRT) >>> Exception Codes: 0x, 0x >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Application Specific Information: >>> abort() called >>> *** Terminating app due to uncaught exception >>> 'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver >>> decodeInt64ForKey:]: value for key (NSTag) is not an integer number' >> >> Well this seems like your nib is corrupted in some fashion. I wouldn't >> expect the preferences or app support to make a scrap of difference here. >> Try asking your customer to re-install to see if they're got a corrupted >> copy of the app. > > Are you sure? It could also be the restorable state that's corrupted. > > Martin, have your user hold the Shift key when launching your app. This > will bypass state restoration, with the caveat that your app will not > restore any unsaved untitled documents that were open at the time of the > crash. I'll have them do that, though just replacing the app with a fresh download worked. Good to know about this shift-key trick in any case. Martin smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
On Mon, Oct 1, 2012, at 07:20 AM, Mike Abdullah wrote: > > On 1 Oct 2012, at 13:13, Martin Hewitson > wrote: > > > Oops, sorry, I chopped off the top of the report. Here it is: > > > > Exception Type: EXC_CRASH (SIGABRT) > > Exception Codes: 0x, 0x > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > > > Application Specific Information: > > abort() called > > *** Terminating app due to uncaught exception > > 'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver > > decodeInt64ForKey:]: value for key (NSTag) is not an integer number' > > Well this seems like your nib is corrupted in some fashion. I wouldn't > expect the preferences or app support to make a scrap of difference here. > Try asking your customer to re-install to see if they're got a corrupted > copy of the app. Are you sure? It could also be the restorable state that's corrupted. Martin, have your user hold the Shift key when launching your app. This will bypass state restoration, with the caveat that your app will not restore any unsaved untitled documents that were open at the time of the crash. --Kyle Sluder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
On Oct 1, 2012, at 11:11 AM, Martin Hewitson wrote: > Is there a way that the XIB files can get corrupted when the app crashes? An app can do anything that the kernel permits it to. A crash is, pretty much by definition, a sign that the app is going wild. It's confused. It's doing stuff it wasn't intended to do. It may be sending arbitrary messages to arbitrary objects or the like. It may be executing data as though it were code. All of that said, it would be fairly surprising if the app had the NIB already open for writing, making it fairly unlikely that it would modify it. And if the user account doesn't have write permission to the app bundle, then the kernel won't allow it, no matter what an out-of-control app might try to do. Regards, Ken ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
On Oct 1, 2012, at 9:11 AM, Martin Hewitson wrote: > I can check, but as I say, it was working fine. It just stopped being able to > launch after a crash. Is there a way that the XIB files can get corrupted > when the app crashes? No. Files in the app bundle are never opened with write access. Typically users won’t even have permission to modify files in the app bundle (if the app is in /Applications.) I hate to sound alarmist, but my first guess would be filesystem corruption. Ask the customer to run Disk Utility and verify the volume. —Jens smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
On Oct 1, 2012, at 10:20 AM, Mike Abdullah wrote: > > On 1 Oct 2012, at 13:13, Martin Hewitson wrote: > >> Oops, sorry, I chopped off the top of the report. Here it is: >> >> Exception Type: EXC_CRASH (SIGABRT) >> Exception Codes: 0x, 0x >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >> >> Application Specific Information: >> abort() called >> *** Terminating app due to uncaught exception >> 'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver >> decodeInt64ForKey:]: value for key (NSTag) is not an integer number' > > Well this seems like your nib is corrupted in some fashion. I wouldn't expect > the preferences or app support to make a scrap of difference here. Try asking > your customer to re-install to see if they're got a corrupted copy of the app. The app was working, then stopped working. Then they downloaded it again, and it worked again. Most strange. > > If not, go through your main menu xib carefully and look for any objects that > somehow have a non-integer tag perhaps. > I can check, but as I say, it was working fine. It just stopped being able to launch after a crash. Is there a way that the XIB files can get corrupted when the app crashes? Thanks for your thoughts on this. Martin Martin Hewitson Albert-Einstein-Institut Max-Planck-Institut fuer Gravitationsphysik und Universitaet Hannover Callinstr. 38, 30167 Hannover, Germany Tel: +49-511-762-17121, Fax: +49-511-762-5861 E-Mail: martin.hewit...@aei.mpg.de WWW: http://www.aei.mpg.de/~hewitson smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
On 1 Oct 2012, at 13:13, Martin Hewitson wrote: > Oops, sorry, I chopped off the top of the report. Here it is: > > Exception Type: EXC_CRASH (SIGABRT) > Exception Codes: 0x, 0x > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Application Specific Information: > abort() called > *** Terminating app due to uncaught exception > 'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver > decodeInt64ForKey:]: value for key (NSTag) is not an integer number' Well this seems like your nib is corrupted in some fashion. I wouldn't expect the preferences or app support to make a scrap of difference here. Try asking your customer to re-install to see if they're got a corrupted copy of the app. If not, go through your main menu xib carefully and look for any objects that somehow have a non-integer tag perhaps. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App won't launch after a crash
Oops, sorry, I chopped off the top of the report. Here it is: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver decodeInt64ForKey:]: value for key (NSTag) is not an integer number' On Oct 1, 2012, at 07:41 AM, Mike Abdullah wrote: > What's the exception? Should appear in the console log somewhere. > > On 1 Oct 2012, at 12:17, Martin Hewitson wrote: > >> Dear all, >> >> I've received a report from a user saying that, after a crash, the app won't >> launch any more. The crash log looks like below. It looks to me like the app >> bundle has somehow got corrupted, but I've no idea what's going on really. >> The user has tried deleting preferences and app support directory, but it >> didn't help. In the end, I suggested downloading the app again. The user did >> that, and it launches now. >> >> Does anyone have a clue what's happening here? >> >> Cheers, >> >> Martin >> >> >> 0 CoreFoundation 0x7fff83ff9784 >> __exceptionPreprocess + 180 >> 1 libobjc.A.dylib 0x7fff88ff2f03 >> objc_exception_throw + 45 >> 2 CoreFoundation 0x7fff83ff95a7 >> +[NSException raise:format:arguments:] + 103 >> 3 CoreFoundation 0x7fff83ff9534 >> +[NSException raise:format:] + 148 >> 4 Foundation 0x7fff853d0075 _decodeInt64 >> + 307 >> 5 AppKit 0x7fff869cf21c -[NSMenuItem >> initWithCoder:] + 1765 >> 6 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 7 Foundation 0x7fff853c9a89 >> -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 >> 8 Foundation 0x7fff853c9fc9 >> -[NSArray(NSArray) initWithCoder:] + 462 >> 9 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 10 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 11 AppKit 0x7fff869d3499 -[NSMenu >> initWithCoder:] + 442 >> 12 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 13 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 14 AppKit 0x7fff869cf2b3 -[NSMenuItem >> initWithCoder:] + 1916 >> 15 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 16 Foundation 0x7fff853c9a89 >> -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 >> 17 Foundation 0x7fff853c9fc9 >> -[NSArray(NSArray) initWithCoder:] + 462 >> 18 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 19 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 20 AppKit 0x7fff869d3499 -[NSMenu >> initWithCoder:] + 442 >> 21 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 22 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 23 AppKit 0x7fff869cf238 -[NSMenuItem >> initWithCoder:] + 1793 >> 24 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 25 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 26 AppKit 0x7fff869cb1e4 >> -[NSNibConnector initWithCoder:] + 406 >> 27 AppKit 0x7fff869cea46 >> -[NSNibControlConnector initWithCoder:] + 788 >> 28 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 29 Foundation 0x7fff853c9a89 >> -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 >> 30 Foundation 0x7fff853c9fc9 >> -[NSArray(NSArray) initWithCoder:] + 462 >> 31 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 32 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 33 AppKit 0x7fff869ca351 >> -[NSIBObjectData initWithCoder:] + 2046 >> 34 Foundation 0x7fff853c8d83 >> _decodeObjectBinary + 2548 >> 35 Foundation 0x7fff853c81fd >> _decodeObject + 208 >> 36 AppKit 0x7fff869c9a41 loadNib + 146 >> 37 AppKit
Re: App won't launch after a crash
What's the exception? Should appear in the console log somewhere. On 1 Oct 2012, at 12:17, Martin Hewitson wrote: > Dear all, > > I've received a report from a user saying that, after a crash, the app won't > launch any more. The crash log looks like below. It looks to me like the app > bundle has somehow got corrupted, but I've no idea what's going on really. > The user has tried deleting preferences and app support directory, but it > didn't help. In the end, I suggested downloading the app again. The user did > that, and it launches now. > > Does anyone have a clue what's happening here? > > Cheers, > > Martin > > > 0 CoreFoundation 0x7fff83ff9784 > __exceptionPreprocess + 180 > 1 libobjc.A.dylib 0x7fff88ff2f03 > objc_exception_throw + 45 > 2 CoreFoundation 0x7fff83ff95a7 > +[NSException raise:format:arguments:] + 103 > 3 CoreFoundation 0x7fff83ff9534 > +[NSException raise:format:] + 148 > 4 Foundation 0x7fff853d0075 _decodeInt64 > + 307 > 5 AppKit 0x7fff869cf21c -[NSMenuItem > initWithCoder:] + 1765 > 6 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 7 Foundation 0x7fff853c9a89 > -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 > 8 Foundation 0x7fff853c9fc9 > -[NSArray(NSArray) initWithCoder:] + 462 > 9 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 10 Foundation 0x7fff853c81fd > _decodeObject + 208 > 11 AppKit 0x7fff869d3499 -[NSMenu > initWithCoder:] + 442 > 12 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 13 Foundation 0x7fff853c81fd > _decodeObject + 208 > 14 AppKit 0x7fff869cf2b3 -[NSMenuItem > initWithCoder:] + 1916 > 15 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 16 Foundation 0x7fff853c9a89 > -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 > 17 Foundation 0x7fff853c9fc9 > -[NSArray(NSArray) initWithCoder:] + 462 > 18 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 19 Foundation 0x7fff853c81fd > _decodeObject + 208 > 20 AppKit 0x7fff869d3499 -[NSMenu > initWithCoder:] + 442 > 21 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 22 Foundation 0x7fff853c81fd > _decodeObject + 208 > 23 AppKit 0x7fff869cf238 -[NSMenuItem > initWithCoder:] + 1793 > 24 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 25 Foundation 0x7fff853c81fd > _decodeObject + 208 > 26 AppKit 0x7fff869cb1e4 > -[NSNibConnector initWithCoder:] + 406 > 27 AppKit 0x7fff869cea46 > -[NSNibControlConnector initWithCoder:] + 788 > 28 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 29 Foundation 0x7fff853c9a89 > -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 > 30 Foundation 0x7fff853c9fc9 > -[NSArray(NSArray) initWithCoder:] + 462 > 31 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 32 Foundation 0x7fff853c81fd > _decodeObject + 208 > 33 AppKit 0x7fff869ca351 > -[NSIBObjectData initWithCoder:] + 2046 > 34 Foundation 0x7fff853c8d83 > _decodeObjectBinary + 2548 > 35 Foundation 0x7fff853c81fd > _decodeObject + 208 > 36 AppKit 0x7fff869c9a41 loadNib + 146 > 37 AppKit 0x7fff869c8fa1 > +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 248 > 38 AppKit 0x7fff869c8dd9 > +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 326 > 39 AppKit 0x7fff869c635b > NSApplicationMain + 279 > > > > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)list
App won't launch after a crash
Dear all, I've received a report from a user saying that, after a crash, the app won't launch any more. The crash log looks like below. It looks to me like the app bundle has somehow got corrupted, but I've no idea what's going on really. The user has tried deleting preferences and app support directory, but it didn't help. In the end, I suggested downloading the app again. The user did that, and it launches now. Does anyone have a clue what's happening here? Cheers, Martin 0 CoreFoundation 0x7fff83ff9784 __exceptionPreprocess + 180 1 libobjc.A.dylib 0x7fff88ff2f03 objc_exception_throw + 45 2 CoreFoundation 0x7fff83ff95a7 +[NSException raise:format:arguments:] + 103 3 CoreFoundation 0x7fff83ff9534 +[NSException raise:format:] + 148 4 Foundation 0x7fff853d0075 _decodeInt64 + 307 5 AppKit 0x7fff869cf21c -[NSMenuItem initWithCoder:] + 1765 6 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 7 Foundation 0x7fff853c9a89 -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 8 Foundation 0x7fff853c9fc9 -[NSArray(NSArray) initWithCoder:] + 462 9 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 10 Foundation 0x7fff853c81fd _decodeObject + 208 11 AppKit 0x7fff869d3499 -[NSMenu initWithCoder:] + 442 12 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 13 Foundation 0x7fff853c81fd _decodeObject + 208 14 AppKit 0x7fff869cf2b3 -[NSMenuItem initWithCoder:] + 1916 15 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 16 Foundation 0x7fff853c9a89 -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 17 Foundation 0x7fff853c9fc9 -[NSArray(NSArray) initWithCoder:] + 462 18 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 19 Foundation 0x7fff853c81fd _decodeObject + 208 20 AppKit 0x7fff869d3499 -[NSMenu initWithCoder:] + 442 21 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 22 Foundation 0x7fff853c81fd _decodeObject + 208 23 AppKit 0x7fff869cf238 -[NSMenuItem initWithCoder:] + 1793 24 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 25 Foundation 0x7fff853c81fd _decodeObject + 208 26 AppKit 0x7fff869cb1e4 -[NSNibConnector initWithCoder:] + 406 27 AppKit 0x7fff869cea46 -[NSNibControlConnector initWithCoder:] + 788 28 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 29 Foundation 0x7fff853c9a89 -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1229 30 Foundation 0x7fff853c9fc9 -[NSArray(NSArray) initWithCoder:] + 462 31 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 32 Foundation 0x7fff853c81fd _decodeObject + 208 33 AppKit 0x7fff869ca351 -[NSIBObjectData initWithCoder:] + 2046 34 Foundation 0x7fff853c8d83 _decodeObjectBinary + 2548 35 Foundation 0x7fff853c81fd _decodeObject + 208 36 AppKit 0x7fff869c9a41 loadNib + 146 37 AppKit 0x7fff869c8fa1 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 248 38 AppKit 0x7fff869c8dd9 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 326 39 AppKit 0x7fff869c635b NSApplicationMain + 279 smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
