crash when loading nib

  • OK, I have no idea why this is failing here. If the lower stacks look
    odd, it is because I am calling [NSDocument newDocument:] in code. The
    New... menu item sends its action to my app controller, which has to
    get some additional information (paths to two files that are parsed as
    a necessary part of creating the new document) via a custom New...
    panel.

    What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    could happen in -isOpaque? Where do I look for possible sources of the
    problem? The nib looks fine in IB.

    This is an application that does NOTHING so far -- all I have is a user
    interface and skeletal controller code -- the minimum complexity I can
    manage and still have the U.I. load up properly.

    #0  0x9313f580 in -[NSSplitView isOpaque] ()
    #1  0x9318bee0 in -[NSSplitView _setIsGrabber:] ()
    #2  0x9318bad8 in -[NSSplitView _compatibility_initWithUnkeyedCoder:] ()
    #3  0x9318b7f0 in -[NSSplitView initWithCoder:] ()

    #32 0x907e4cf8 in _decodeObject ()
    #33 0x907e552c in _decodeValueOfObjCType ()
    #34 0x907e6ab0 in -[NSUnarchiver decodeValuesOfObjCTypes:] ()
    #35 0x930d50d4 in -[NSTextContainer setLineFragmentPadding:] ()
    #36 0x907e4cf8 in _decodeObject ()
    #37 0x93124524 in -[NSMenuItem keyEquivalentModifierMask] ()
    #38 0x930eaa2c in +[NSBundle(NSNibLoading)
    _loadNibFile:nameTable:withZone:ownerBundle:] ()
    #39 0x93149a5c in +[NSBundle(NSNibLoading)
    loadNibFile:externalNameTable:withZone:] ()
    #40 0x931c7214 in -[NSWindowController loadWindow] ()
    #41 0x931c6ffc in -[NSWindowController window] ()
    #42 0x931ca1a4 in -[NSWindowController showWindow:] ()
    #43 0x931ca164 in -[NSDocument showWindows] ()
    #44 0x931f06c8 in -[NSDocumentController
    openUntitledDocumentOfType:display:] ()
    #45 0x93284b54 in -[NSDocumentController newDocument:] ()
    #46 0x930f9cac in -[NSApplication sendAction:to:from:] ()
    #47 0x000065e8 in -[SCNewDocumentPanelController
    completeOpenNewDocument:] (self=0x3799b0, _cmd=0x9dba0,
    sender=0x37b2f0) at
    SCNewDocumentPanelController.m:106/Volumes/Clarke/Users/
    brentgulanowski/Programming/astro/projects/SCatalogue/

    --
    Brent Gulanowski                <brentgulanowski...>
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • In my cocoa/java app I found that using NSWindowController methods to
    load a nib caused crashes under MacOS 10.1. The solution was to load
    the nib using the NSApplication methods.

    just in case that is helpful,
    dustin

    On Thursday, June 19, 2003, at 01:55 AM, Brent Gulanowski wrote:

    > OK, I have no idea why this is failing here. If the lower stacks look
    > odd, it is because I am calling [NSDocument newDocument:] in code. The
    > New... menu item sends its action to my app controller, which has to
    > get some additional information (paths to two files that are parsed as
    > a necessary part of creating the new document) via a custom New...
    > panel.
    >
    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a
    > user interface and skeletal controller code -- the minimum complexity
    > I can manage and still have the U.I. load up properly.
    >
    > #0  0x9313f580 in -[NSSplitView isOpaque] ()
    > #1  0x9318bee0 in -[NSSplitView _setIsGrabber:] ()
    > #2  0x9318bad8 in -[NSSplitView _compatibility_initWithUnkeyedCoder:]
    > ()
    > #3  0x9318b7f0 in -[NSSplitView initWithCoder:] ()
    >
    > #32 0x907e4cf8 in _decodeObject ()
    > #33 0x907e552c in _decodeValueOfObjCType ()
    > #34 0x907e6ab0 in -[NSUnarchiver decodeValuesOfObjCTypes:] ()
    > #35 0x930d50d4 in -[NSTextContainer setLineFragmentPadding:] ()
    > #36 0x907e4cf8 in _decodeObject ()
    > #37 0x93124524 in -[NSMenuItem keyEquivalentModifierMask] ()
    > #38 0x930eaa2c in +[NSBundle(NSNibLoading)
    > _loadNibFile:nameTable:withZone:ownerBundle:] ()
    > #39 0x93149a5c in +[NSBundle(NSNibLoading)
    > loadNibFile:externalNameTable:withZone:] ()
    > #40 0x931c7214 in -[NSWindowController loadWindow] ()
    > #41 0x931c6ffc in -[NSWindowController window] ()
    > #42 0x931ca1a4 in -[NSWindowController showWindow:] ()
    > #43 0x931ca164 in -[NSDocument showWindows] ()
    > #44 0x931f06c8 in -[NSDocumentController
    > openUntitledDocumentOfType:display:] ()
    > #45 0x93284b54 in -[NSDocumentController newDocument:] ()
    > #46 0x930f9cac in -[NSApplication sendAction:to:from:] ()
    > #47 0x000065e8 in -[SCNewDocumentPanelController
    > completeOpenNewDocument:] (self=0x3799b0, _cmd=0x9dba0,
    > sender=0x37b2f0) at
    > SCNewDocumentPanelController.m:106/Volumes/Clarke/Users/
    > brentgulanowski/Programming/astro/projects/SCatalogue/
    >
    > --
    > Brent Gulanowski                <brentgulanowski...>
    > _______________________________________________
    > cocoa-dev mailing list | <cocoa-dev...>
    > Help/Unsubscribe/Archives:
    > http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    > Do not post admin requests to the list. They will be ignored.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On Thursday, June 19, 2003, at 04:24  AM, Dustin Sacks wrote:

    > In my cocoa/java app I found that using NSWindowController methods to
    > load a nib caused crashes under MacOS 10.1. The solution was to load
    > the nib using the NSApplication methods.
    >
    > just in case that is helpful,
    > dustin

    Which methods are those? I can't see any that would load a bundle for
    me. Only NSBundle itself does that, and NSWindowController just calls
    NSBundle.

    --
    Brent Gulanowski                <brentgulanowski...>

    http://inkubator.idevgames.com/
    Working together to make great software.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • Due to a bug in the keyed archiving, using the new nib format in IB can
    result in random crashes. This has been fixed in 10.2.6.

    Change the preference in IB to use the pre-10.2 nib format and resave
    your nib files.

    Henri Lamiraux
    Engineering Manager
    User Interface Tools Group
    Apple

    On June 18, 2003, at 10:55 PM, Brent Gulanowski wrote:

    > OK, I have no idea why this is failing here. If the lower stacks look
    > odd, it is because I am calling [NSDocument newDocument:] in code. The
    > New... menu item sends its action to my app controller, which has to
    > get some additional information (paths to two files that are parsed as
    > a necessary part of creating the new document) via a custom New...
    > panel.
    >
    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a
    > user interface and skeletal controller code -- the minimum complexity
    > I can manage and still have the U.I. load up properly.
    >
    > #0  0x9313f580 in -[NSSplitView isOpaque] ()
    > #1  0x9318bee0 in -[NSSplitView _setIsGrabber:] ()
    > #2  0x9318bad8 in -[NSSplitView _compatibility_initWithUnkeyedCoder:]
    > ()
    > #3  0x9318b7f0 in -[NSSplitView initWithCoder:] ()
    >
    > #32 0x907e4cf8 in _decodeObject ()
    > #33 0x907e552c in _decodeValueOfObjCType ()
    > #34 0x907e6ab0 in -[NSUnarchiver decodeValuesOfObjCTypes:] ()
    > #35 0x930d50d4 in -[NSTextContainer setLineFragmentPadding:] ()
    > #36 0x907e4cf8 in _decodeObject ()
    > #37 0x93124524 in -[NSMenuItem keyEquivalentModifierMask] ()
    > #38 0x930eaa2c in +[NSBundle(NSNibLoading)
    > _loadNibFile:nameTable:withZone:ownerBundle:] ()
    > #39 0x93149a5c in +[NSBundle(NSNibLoading)
    > loadNibFile:externalNameTable:withZone:] ()
    > #40 0x931c7214 in -[NSWindowController loadWindow] ()
    > #41 0x931c6ffc in -[NSWindowController window] ()
    > #42 0x931ca1a4 in -[NSWindowController showWindow:] ()
    > #43 0x931ca164 in -[NSDocument showWindows] ()
    > #44 0x931f06c8 in -[NSDocumentController
    > openUntitledDocumentOfType:display:] ()
    > #45 0x93284b54 in -[NSDocumentController newDocument:] ()
    > #46 0x930f9cac in -[NSApplication sendAction:to:from:] ()
    > #47 0x000065e8 in -[SCNewDocumentPanelController
    > completeOpenNewDocument:] (self=0x3799b0, _cmd=0x9dba0,
    > sender=0x37b2f0) at
    > SCNewDocumentPanelController.m:106/Volumes/Clarke/Users/
    > brentgulanowski/Programming/astro/projects/SCatalogue/
    >
    > --
    > Brent Gulanowski                <brentgulanowski...>
    > _______________________________________________
    > cocoa-dev mailing list | <cocoa-dev...>
    > Help/Unsubscribe/Archives:
    > http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    > Do not post admin requests to the list. They will be ignored.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On Thursday, June 19, 2003, at 10:29  AM, Henri Lamiraux wrote:

    > Due to a bug in the keyed archiving, using the new nib format in IB
    > can result in random crashes. This has been fixed in 10.2.6.
    >
    > Change the preference in IB to use the pre-10.2 nib format and resave
    > your nib files.
    >
    > Henri Lamiraux
    > Engineering Manager
    > User Interface Tools Group
    > Apple
    >

    Hate to be a downer, but that setting was already selected. Isn't that
    why it's using the compatibility method:

    >> #2  0x9318bad8 in -[NSSplitView _compatibility_initWithUnkeyedCoder:]
    >> ()

    Also I am using 10.2.6.

    What does that mean?

    > On June 18, 2003, at 10:55 PM, Brent Gulanowski wrote (some stuff)
    >
    --
    Brent Gulanowski                <brentgulanowski...>

    The monsters in Doom are simply mean: nobody is interested in knowing
    why they behave in that particular way: it may be genetic or maybe they
    are just fed up with intergalactic imperialists that keep sending space
    marines to kill them all. - Gonzalo Frasca
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On Thursday, June 19, 2003, at 10:29  AM, Henri Lamiraux wrote:

    > Due to a bug in the keyed archiving, using the new nib format in IB
    > can result in random crashes. This has been fixed in 10.2.6.
    >
    > Change the preference in IB to use the pre-10.2 nib format and resave
    > your nib files.

    So I tried switching the preference to "both" and re-saving, and when I
    run, I still get the same crash:
    #0  0x9313f580 in -[NSSplitView isOpaque] ()
    #1  0x9318bee0 in -[NSSplitView _setIsGrabber:] ()
    #2  0x9318b8b8 in -[NSSplitView initWithCoder:] ()
    #3  0x908103ec in _decodeObjectBinary ()
    #4  0x908185d4 in _decodeObject ()
    #5  0x930e2f74 in -[NSResponder initWithCoder:] ()
    #6  0x930ad8c0 in -[NSView initWithCoder:] ()
    #7  0x9318b820 in -[NSSplitView initWithCoder:] ()
    #8  0x908103ec in _decodeObjectBinary ()
    #9  0x9083cb0c in -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] ()

    Is there a problem with nesting split views, by any chance?

    Thanks,
    --
    Brent Gulanowski                <brentgulanowski...>

    http://inkubator.idevgames.com/
    Working together to make great software.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • Yes sorry I noticed that just when I was pressing the send button.

    Henri Lamiraux
    Engineering Manager
    User Interface Tools Group
    Apple

    On June 19, 2003, at 7:44 AM, Brent Gulanowski wrote:

    >
    > On Thursday, June 19, 2003, at 10:29  AM, Henri Lamiraux wrote:
    >
    >> Due to a bug in the keyed archiving, using the new nib format in IB
    >> can result in random crashes. This has been fixed in 10.2.6.
    >>
    >> Change the preference in IB to use the pre-10.2 nib format and resave
    >> your nib files.
    >>
    >> Henri Lamiraux
    >> Engineering Manager
    >> User Interface Tools Group
    >> Apple
    >>
    >
    > Hate to be a downer, but that setting was already selected. Isn't that
    > why it's using the compatibility method:
    >
    >>> #2  0x9318bad8 in -[NSSplitView
    >>> _compatibility_initWithUnkeyedCoder:] ()
    >
    > Also I am using 10.2.6.
    >
    > What does that mean?
    >
    >> On June 18, 2003, at 10:55 PM, Brent Gulanowski wrote (some stuff)
    >>
    > --
    > Brent Gulanowski                <brentgulanowski...>
    >
    > The monsters in Doom are simply mean: nobody is interested in knowing
    > why they behave in that particular way: it may be genetic or maybe
    > they are just fed up with intergalactic imperialists that keep sending
    > space marines to kill them all. - Gonzalo Frasca
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • :-)

    Well, the problem just went away. First I tried to build a whole new
    nib, and I got the same crash. Then as I said I switched to the other
    nib format, and still crashed. Then I went back to my original nib,
    deleted all the split views, and tried -> worked. Added one split view
    -> worked. Stuck inside another split view, taking me back to how I was
    -> worked. WTF?! Whatever, it works for now.

    Thanks

    On Thursday, June 19, 2003, at 10:50  AM, Henri Lamiraux wrote:

    > Yes sorry I noticed that just when I was pressing the send button.

    --
    Brent Gulanowski                <brentgulanowski...>

    http://inkubator.idevgames.com/
    Working together to make great software.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On 6/18/03 11:55 PM, "Brent Gulanowski" <brentg...> wrote:

    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a user
    > interface and skeletal controller code -- the minimum complexity I can
    > manage and still have the U.I. load up properly.

    I have no idea as to why this happens, I can only confirm that the exact
    same thing happens to my nib.  It happens in the same place (-[NSSplitView
    isOpaque] ()).

    See my note below for things that I've tried without success.

    The only solution that I've found is this: (I use CVS for version control,
    so this makes the solution easier)

    1) Make a single, small change in the nib file.
    2) Build and run it to make sure it doesn't crash.
    3) If crashes, delete it and checkout a copy from CVS, go to step 1.
    4) If it doesn't crash, check it into CVS.
    5) For next change, go to step 1.

    This may seem tedious (and believe me it is), but it is the _ONLY_ (and I
    really stress "ONLY") way that I have found to keep my nib from getting
    corrupted.  I've found that once a nib becomes corrupted, there is no way to
    fix it.  For example, sometimes my nib becomes corrupted when I add a menu
    item to the main menu bar.  If I then delete the menu item to try and fix
    the corrupted nib, it does not work, the nib is still corrupted.

    I realize that my solution may not work for you because you may not have an
    older working nib to go back to, so you may just have to recreate it.  If
    anyone else knows of any way to fix a corrupted nib file then please let us
    know how to do it.

    Luckily I've only had this problem with one nib file so far, but it's been
    one pain in the @$$.

    Note:  My nib file is in the Pre-10.2 format.  I've tried using the 10.2
    format (even though it has problems) and that didn't work.  I've tried
    checking the nib with nibtool (it checks out fine), creating a new nib with
    nibtool (it still crashes), and probably a few other things that I can't
    think of.

    ____________________________________

    Dave Thorup
    Software Engineer
    <dave...>

    www.kuwan.net
    Defaults Manager - The premier editor for Mac OS X's User Defaults /
    Preferences database.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • If you still have it could you send me the nib that was crashing?

    Thanks

    Henri Lamiraux
    Engineering Manager
    User Interface Tools Group
    Apple

    On June 19, 2003, at 8:03 AM, Brent Gulanowski wrote:

    > :-)
    >
    > Well, the problem just went away. First I tried to build a whole new
    > nib, and I got the same crash. Then as I said I switched to the other
    > nib format, and still crashed. Then I went back to my original nib,
    > deleted all the split views, and tried -> worked. Added one split view
    > -> worked. Stuck inside another split view, taking me back to how I
    > was -> worked. WTF?! Whatever, it works for now.
    >
    > Thanks
    >
    > On Thursday, June 19, 2003, at 10:50  AM, Henri Lamiraux wrote:
    >
    >> Yes sorry I noticed that just when I was pressing the send button.
    >
    > --
    > Brent Gulanowski                <brentgulanowski...>
    >
    > http://inkubator.idevgames.com/
    > Working together to make great software.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • I think this is an NSSplitView bug. Try changing the type of
    the splitter widget in IB.

    Simon

    Brent Gulanowski wrote:

    > OK, I have no idea why this is failing here. If the lower stacks look
    > odd, it is because I am calling [NSDocument newDocument:] in code. The
    > New... menu item sends its action to my app controller, which has to
    > get some additional information (paths to two files that are parsed as
    > a necessary part of creating the new document) via a custom New...
    > panel.
    >
    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a user
    > interface and skeletal controller code -- the minimum complexity I can
    > manage and still have the U.I. load up properly.
    >
    > #0  0x9313f580 in -[NSSplitView isOpaque] ()
    > #1  0x9318bee0 in -[NSSplitView _setIsGrabber:] ()
    > #2  0x9318bad8 in -[NSSplitView _compatibility_initWithUnkeyedCoder:] ()
    > #3  0x9318b7f0 in -[NSSplitView initWithCoder:] ()
    >
    > #32 0x907e4cf8 in _decodeObject ()
    > #33 0x907e552c in _decodeValueOfObjCType ()
    > #34 0x907e6ab0 in -[NSUnarchiver decodeValuesOfObjCTypes:] ()
    > #35 0x930d50d4 in -[NSTextContainer setLineFragmentPadding:] ()
    > #36 0x907e4cf8 in _decodeObject ()
    > #37 0x93124524 in -[NSMenuItem keyEquivalentModifierMask] ()
    > #38 0x930eaa2c in +[NSBundle(NSNibLoading)
    > _loadNibFile:nameTable:withZone:ownerBundle:] ()
    > #39 0x93149a5c in +[NSBundle(NSNibLoading)
    > loadNibFile:externalNameTable:withZone:] ()
    > #40 0x931c7214 in -[NSWindowController loadWindow] ()
    > #41 0x931c6ffc in -[NSWindowController window] ()
    > #42 0x931ca1a4 in -[NSWindowController showWindow:] ()
    > #43 0x931ca164 in -[NSDocument showWindows] ()
    > #44 0x931f06c8 in -[NSDocumentController
    > openUntitledDocumentOfType:display:] ()
    > #45 0x93284b54 in -[NSDocumentController newDocument:] ()
    > #46 0x930f9cac in -[NSApplication sendAction:to:from:] ()
    > #47 0x000065e8 in -[SCNewDocumentPanelController
    > completeOpenNewDocument:] (self=0x3799b0, _cmd=0x9dba0,
    > sender=0x37b2f0) at
    > SCNewDocumentPanelController.m:106/Volumes/Clarke/Users/
    > brentgulanowski/Programming/astro/projects/SCatalogue/
    >
    > --
    > Brent Gulanowski                                <brentgulanowski...>
    > _______________________________________________
    > cocoa-dev mailing list | <cocoa-dev...>
    > Help/Unsubscribe/Archives:
    > http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    > Do not post admin requests to the list. They will be ignored.

    --
    Simon Fraser
    Entomologist
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On Thursday, June 19, 2003, at 7:44 AM, Brent Gulanowski wrote:

    > On Thursday, June 19, 2003, at 10:29  AM, Henri Lamiraux wrote:
    >
    >> Due to a bug in the keyed archiving, using the new nib format in IB
    >> can result in random crashes. This has been fixed in 10.2.6.
    >>
    >> Change the preference in IB to use the pre-10.2 nib format and resave
    >> your nib files.
    >>
    >> Henri Lamiraux
    >> Engineering Manager
    >> User Interface Tools Group
    >> Apple
    >>
    >
    > Hate to be a downer, but that setting was already selected. Isn't that
    > why it's using the compatibility method:
    >
    >>> #2  0x9318bad8 in -[NSSplitView
    >>> _compatibility_initWithUnkeyedCoder:] ()
    >
    > Also I am using 10.2.6.
    >
    > What does that mean?
    >
    >> On June 18, 2003, at 10:55 PM, Brent Gulanowski wrote (some stuff)
    >>
    > --
    If you made the nib on a system older than 10.2.6 its also going to
    quite possibly be messed up.

    vince
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On 6/18/03 11:55 PM, "Brent Gulanowski" <brentg...> wrote:

    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a user
    > interface and skeletal controller code -- the minimum complexity I can
    > manage and still have the U.I. load up properly.

    I have no idea as to why this happens, I can only confirm that the exact
    same thing happens to my nib.  It happens in the same place (-[NSSplitView
    isOpaque] ()).

    See my note below for things that I've tried without success.

    The only solution that I've found is this: (I use CVS for version control,
    so this makes the solution easier)

    1) Make a single, small change in the nib file.
    2) Build and run it to make sure it doesn't crash.
    3) If crashes, delete it and checkout a copy from CVS, go to step 1.
    4) If it doesn't crash, check it into CVS.
    5) For next change, go to step 1.

    This may seem tedious (and believe me it is), but it is the _ONLY_ (and I
    really stress "ONLY") way that I have found to keep my nib from getting
    corrupted.  I've found that once a nib becomes corrupted, there is no way to
    fix it.  For example, sometimes my nib becomes corrupted when I add a menu
    item to the main menu bar.  If I then delete the menu item to try and fix
    the corrupted nib, it does not work, the nib is still corrupted.

    I realize that my solution may not work for you because you may not have an
    older working nib to go back to, so you may just have to recreate it.  If
    anyone else knows of any way to fix a corrupted nib file then please let us
    know how to do it.

    Luckily I've only had this problem with one nib file so far, but it's been
    one pain in the @$$.

    Note:  My nib file is in the Pre-10.2 format.  I've tried using the 10.2
    format (even though it has problems) and that didn't work.  I've tried
    checking the nib with nibtool (it checks out fine), creating a new nib with
    nibtool (it still crashes), and probably a few other things that I can't
    think of.

    ____________________________________

    Dave Thorup
    Software Engineer
    <dave...>

    www.kuwan.net
    Defaults Manager - The premier editor for Mac OS X's User Defaults /
    Preferences database.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On 6/18/03 11:55 PM, "Brent Gulanowski" <brentg...> wrote:

    > What is going to cause an EXC_BAD_ACCESS while loading a nib? What
    > could happen in -isOpaque? Where do I look for possible sources of the
    > problem? The nib looks fine in IB.
    >
    > This is an application that does NOTHING so far -- all I have is a user
    > interface and skeletal controller code -- the minimum complexity I can
    > manage and still have the U.I. load up properly.

    I have no idea as to why this happens, I can only confirm that the exact
    same thing happens to my nib.  It happens in the same place
    (-[NSSplitView
    isOpaque] ()).

    See my note below for things that I've tried without success.

    The only solution that I've found is this: (I use CVS for version
    control,
    so this makes the solution easier)

    1) Make a single, small change in the nib file.
    2) Build and run it to make sure it doesn't crash.
    3) If crashes, delete it and checkout a copy from CVS, go to step 1.
    4) If it doesn't crash, check it into CVS.
    5) For next change, go to step 1.

    This may seem tedious (and believe me it is), but it is the _ONLY_ (and
    I
    really stress "ONLY") way that I have found to keep my nib from getting
    corrupted.  I've found that once a nib becomes corrupted, there is no
    way to
    fix it.  For example, sometimes my nib becomes corrupted when I add a
    menu
    item to the main menu bar.  If I then delete the menu item to try and
    fix
    the corrupted nib, it does not work, the nib is still corrupted.

    I realize that my solution may not work for you because you may not
    have an
    older working nib to go back to, so you may just have to recreate it.
    If
    anyone else knows of any way to fix a corrupted nib file then please
    let us
    know how to do it.

    Luckily I've only had this problem with one nib file so far, but it's
    been
    one pain in the @$$.

    Note:  My nib file is in the Pre-10.2 format.  I've tried using the
    10.2
    format (even though it has problems) and that didn't work.  I've tried
    checking the nib with nibtool (it checks out fine), creating a new nib
    with
    nibtool (it still crashes), and probably a few other things that I can't
    think of.

    ____________________________________

    Dave Thorup
    Software Engineer
    <dave...>

    www.kuwan.net
    Defaults Manager - The premier editor for Mac OS X's User Defaults /
    Preferences database.
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
  • On 20/6/03 at 4:12 am, David Thorup said:

    > My nib file is in the Pre-10.2 format.  I've tried using the 10.2
    > format (even though it has problems) and that didn't work.

    This is tangential to the original topic of this thread, but can anyone
    tell me a bit more about the problems with the 10.2+ Nib format which
    David alludes to? I wasn't aware there were acknowledged problems with
    the new format.

    (I'll check the list archives too, of course, but there are 20+ pages on
    "10.2 nib problem", so any quick summary would be helpful!)

    Cheers,
    -Matt

    --
    Matt Gemmell
    Scotland Software
    http://www.scotlandsoftware.com/
    _______________________________________________
    cocoa-dev mailing list | <cocoa-dev...>
    Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
    Do not post admin requests to the list. They will be ignored.
previous month june 2003 next month
MTWTFSS
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            
Go to today