Crash in System Preferences

  • I have a customer getting a crash in System Preferences when trying to load
    our prefpane. We can't reproduce it here and have only one report of this.
    What might cause it?

    Command: System Preferences
    Path:    /Applications/System Preferences.app/Contents/MacOS/System
    Preferences
    Parent:  WindowServer [58]

    Version:        3.3 (3.3)
    Build Version:  20
    Project Name:  SystemPrefsApp
    Source Version: 1260100

    PID:    473
    Thread: 0

    Application Specific Information:
    myApp  (com.mycompany.myapp.prefPane)

    Exception:  EXC_BAD_ACCESS (0x0001)
    Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000001

    Thread 0 Crashed:
    .apple.Foundation  0x92bd00b4 -[NSCFString isEqualToString:] + 56
    .apple.AppKit      0x937acb50 -[NSWindow _dosetTitle:andDefeatWrap:] + 264
    .prefPane          0x0587520c -[ComMyPrefPaneClass mainViewDidLoad] + 776
    .preferencepanes  0x946d88f0 -[NSPreferencePane loadMainView] + 204
    .preferencepanes  0x946d8344 -[NSPrefPaneBundle instantiatePrefPaneObject]
    + 416

    This is on OS 10.4.11 but System Prefs 3.3. On my 10.4.9 system System Prefs
    is v3.5 and it of course works fine.

    Any thoughts?

    Trygve
  • On 20 Nov 2007, at 18:01, Trygve Inda wrote:

    > I have a customer getting a crash in System Preferences when trying
    > to load
    > our prefpane. We can't reproduce it here and have only one report of
    > this.
    > What might cause it?

    Looks like a bad object pointer... perhaps you're releasing something
    too soon?  Maybe on 10.4 it just happens to live slightly longer for
    some reason.

    Also:

    > Application Specific Information:
    > myApp  (com.mycompany.myapp.prefPane)
      ^^^^^^  ^^^^^^^^^^^^^^^^^^^^

    Is this program called "MyApp"?  Is your company called "MyCompany"?
    If not, *please* change these to sensible values.  They're supposed to
    be unique, and if people start using the default values, things are
    going to start breaking for users.  (Hint: look in your Info.plist
    files.)

    Kind regards,

    Alastair.

    --
    http://alastairs-place.net
  • > Looks like a bad object pointer... perhaps you're releasing something
    > too soon?  Maybe on 10.4 it just happens to live slightly longer for
    > some reason.

    Since I can't reproduce it here, I can't tell where in our init code it is
    dying... Assuming it even gets that far.

    >
    > Is this program called "MyApp"?  Is your company called "MyCompany"?
    > If not, *please* change these to sensible values.  They're supposed to
    > be unique, and if people start using the default values, things are
    > going to start breaking for users.  (Hint: look in your Info.plist
    > files.)

    The values were changed for this message - they are unique in reality.
  • .prefPane          0x0587520c -[ComMyPrefPaneClass mainViewDidLoad] +
    776

    You may be able to figure out what operation this is if you look at
    the assembly. +776 is an instruction offset.

    --
    m-s

    On 20 Nov, 2007, at 14:53, Trygve Inda wrote:

    >
    >> Looks like a bad object pointer... perhaps you're releasing something
    >> too soon?  Maybe on 10.4 it just happens to live slightly longer for
    >> some reason.
    >
    > Since I can't reproduce it here, I can't tell where in our init code
    > it is
    > dying... Assuming it even gets that far.
    >
    >>
    >> Is this program called "MyApp"?  Is your company called "MyCompany"?
    >> If not, *please* change these to sensible values.  They're supposed
    >> to
    >> be unique, and if people start using the default values, things are
    >> going to start breaking for users.  (Hint: look in your Info.plist
    >> files.)
    >
    > The values were changed for this message - they are unique in reality.
  • On 11/20/07 8:05 PM, "Michael Watson" <mikey-san...> wrote:

    > .prefPane          0x0587520c -[ComMyPrefPaneClass mainViewDidLoad] +
    > 776
    >
    > You may be able to figure out what operation this is if you look at
    > the assembly. +776 is an instruction offset.

    Yup... It may be a debug vs relase thing, but +776 does not seem related to

    .apple.Foundation  0x92bd00b4 -[NSCFString isEqualToString:] + 56
    .apple.AppKit      0x937acb50 -[NSWindow _dosetTitle:andDefeatWrap:] + 264

    Working on it. The crash is on 10.4.11, which works here (and with many
    thousands of other users too).

    Working on it...

    Thanks,

    T.
  • On 20 Nov 2007, at 20:39, Trygve Inda <cocoa...> wrote:

    > On 11/20/07 8:05 PM, "Michael Watson" <mikey-san...> wrote:
    >
    >> .prefPane          0x0587520c -[ComMyPrefPaneClass mainViewDidLoad] +
    >> 776
    >>
    >> You may be able to figure out what operation this is if you look at
    >> the assembly. +776 is an instruction offset.
    >
    > Yup... It may be a debug vs relase thing, but +776 does not seem
    > related to

    [snip]

    Remember to check which processor architecture you're looking at. I
    sometimes forget that there are two options and then spend time
    puzzling over odd offsets.

    Kind regards,

    Alastair

    --
    http://alastairs-place.net
previous month november 2007 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