Skip navigation

Mail.app 4.4 (1082) - EXC_BAD_ACCESS (SIGSEGV) + KERN_INVALID_ADDRESS

5579 Views 17 Replies Latest reply: Nov 22, 2011 5:00 PM by dianeoforegon RSS
1 2 Previous Next
Carmelo Califano Calculating status...
Currently Being Moderated
Dec 21, 2010 2:44 AM
Hi all,
Mail.app has been crashing ever since the latest update to 4.4 (combo update).
Crash reports have been sent to Apple.
Below an excerpt:
Process: Mail [199]
Path: /Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 4.4 (1082)
Build Info: Mail-10820000~1
Code Type: X86-64 (Native)
Parent Process: launchd [150]

Date/Time: 2010-12-21 10:40:09.407 +0100
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000000000018
Crashed Thread: 18 Dispatch queue: com.apple.root.low-priority

Application Specific Information:
objc_msgSend() selector name: _changeValueForKey:usingBlock:
-[IMAPAccount _fetchUnreadCountsCheckForNewMessages:]
-[IMAPGateway _waitForDelayedSelectOperation:]
-[LibraryIMAPStore fetchSynchronously]
-[ComposeBackEnd _saveThreadSaveContents:]

Is this a known defect?

Thanks!
MacBook Pro 15", Mac OS X (10.6.5)
  • tf99 Calculating status...
    I'm having a very similar problem, I think. Mail.app just started crashing for me in the last few days. I assumed it had something to do with my Gmail IMAP account, which is often slow to synchronize with the server (I have both work and a personal Mac syncing with the same accounts). My crash report below, in case it helps; I've bold-faced the elements that seem to differ from the original poster's:



    Process: Mail [704]
    Path: /Applications/Mail.app/Contents/MacOS/Mail
    Identifier: com.apple.mail
    Version: 4.4 (1082)
    Build Info: Mail-10820000~1
    Code Type: X86-64 (Native)
    Parent Process: launchd [166]

    Date/Time: 2011-02-02 09:59:04.948 -0500
    OS Version: Mac OS X *10.6.6 (10J567)*
    Report Version: 6

    *Interval Since Last Report: 64840 sec*
    *Crashes Since Last Report: 1*
    *Per-App Interval Since Last Report: 627702 sec*
    *Per-App Crashes Since Last Report: 1*
    *Anonymous UUID: E8AE1873-A232-4475-8AB8-BAEE8172FC2D*

    Exception Type: EXC_*CRASH (SIGILL*)
    Exception Codes: *0x0000000000000000, 0x0000000000000000*
    Crashed Thread: *0 Dispatch queue: com.apple.main-thread*

    Application Specific Information:
    -[IMAPAccount _fetchUnreadCountsCheckForNewMessages:]
    *-[IMAPMailboxSyncEngine _goWithMessagesIfNeeded:]*
    *-[IMAPAccount fetchSynchronouslyIsAuto:]*
    2.0 GHz MacBook, Mac OS X (10.6.6), 4GB RAM
  • teegeb Calculating status...
    I'm dealing with the same issue, see the thread at:

    http://discussions.apple.com/thread.jspa?threadID=2660758&start=0&tstart=0

    I had submitted a bug report to apple, never heard anything back.

    re http://www.apple.com/feedback/macosx.html - Feedback type, bug report.
    iMac i7, Mac OS X (10.6.6)
  • teegeb Level 1 Level 1 (5 points)
    can you try something, open keychain -> keychain access -> keychain first aid. after running that, does it show any problems (displayed in red)? if so, what were the problems and then repair.
    iMac i7
  • teegeb Level 1 Level 1 (5 points)
    in my situation at least:

    http://discussions.apple.com/thread.jspa?threadID=2660758&tstart=0&messageID=131 07357#13107357

    appears to be related to imap idle command - disabling, crash went away. hope that helps you.
    iMac i7
  • teegeb Level 1 Level 1 (5 points)
    can you include the entire crash log?
    iMac i7
1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.