#947 new
Dirk Ruediger

Mailmate crashes on Yosemite at startup

Reported by Dirk Ruediger | October 29th, 2014 @ 06:54 AM

Since last week (I upgraded to OSX 10.0 a few days before) MailMate crashes at startup. The main window is established and the mail accounts are getting synced (the throbbers are active).

Attached you find a stracktrace as sent to Apple.

Comments and changes to this ticket

  • benny

    benny October 29th, 2014 @ 08:29 AM

    Thanks for the crash report. It's a bug which I would very much like to track down since it's difficult to reproduce (I've seen it once before).

    First, launch MailMate from the Terminal and send me the output after the crash:


    The problem is likely related to a single mailbox. You can take the machine offline and then launch MailMate. That'll allow you to take accounts offline and then you can take them online one by one to find the one with this problem. You can also do this for individual mailboxes and it's likely it is all related to a single mailbox in a single IMAP account.

    Thanks in advance!

  • Dirk Ruediger

    Dirk Ruediger October 29th, 2014 @ 08:56 AM

    I followed your instructions. Here is the dumped output (real names obfuscated):

    $ /Applications/MailMate.app/Contents/MacOS/MailMate
    Fatal: Unexpectedly did not find value 2194
    update_message_location (6/62415): , 0, imap://localname%40mail.domain@mailserver.local/INBOX, 0, 2194
    Dumping virtual headers (and a selection of real headers) for message 62415:
                 #attachments-count: '0'
                      #body-part-id: '62415'
    Dumping selection of real headers for message 62415:
    Value maps are not identical: $Msgs.filter(#source.protocol =[c] 'imap').filter(#uid exists and #uid !=[c] '*')
    Map (differs from verification map):
    Verification map (differs from value map):
      1890: 58048
      2136: 59517
      2188: 62272
      2189: 62276
    Value maps are not identical: $Msgs.filter(#old-source.protocol =[c] 'imap').filter(#old-uid exists)
    Map (differs from verification map):
      2194: 62415
    Verification map (differs from value map):

    I have two accounts in MailMate. So I found the failing account by selectively setting the accounts online.
    Then I set the INBOX offline and set the failing account online. Next I resetted the INBOX while beeing offline and switched it to online state. Everything is working fine again.

    So it was some kind corrupt local cache of the INBOX in one of my mail accounts.

  • benny

    benny October 29th, 2014 @ 03:05 PM

    • State changed from “new” to “cantreproduce”

    Ok, so the problem has resolved itself. That is bad news for me :-) Thanks for the output. I'll see if it provides me with some hints.

  • Dirk Ruediger

    Dirk Ruediger October 29th, 2014 @ 03:17 PM

    I might restore my MailMate-"database" from yesterdays/last-weeks backup. If you provide information for a more detailled log or stacktrace, then it would be worth the effort.

  • benny

    benny October 30th, 2014 @ 01:40 PM

    When looking into this issue I found out that I already added some extra code to track down this bug. If you can still reproduce it then enable this debug variable:

    defaults write com.freron.MailMate MmGenerateServerLogsBeforeCrash -bool YES

    If it works then it should generate mailmate_server_logs.tar.gz which you send to me using “Help ▸ Send Feedback”.

    Thanks in advance!

  • Dirk Ruediger

    Dirk Ruediger November 3rd, 2014 @ 03:00 PM

    Do you still need my "corrupt" mail account for logfiles or debugging? Otherwise I will repair it by resetting the INBOX again.

    I'm missing a working mailmate. ;)

    Best regards

  • Dirk Ruediger

    Dirk Ruediger November 4th, 2014 @ 09:28 AM

    Today I didn't get it managed to reset the INBOX as described above.
    So I deleted the IMAP account and imported it using the MailMate import wizzard.
    When choosing the Mail.app IMAP account MailMate crashed again. Then I used the Thunderbird account (I had to use this app since the OSX 10.10 upgrade) and it worked. I hope that information helps.

  • benny

    benny November 4th, 2014 @ 09:58 AM

    Very sorry for the delayed response! I reviewed the data, but I didn't see a clear way forward. It is somehow related to messages having been deleted server-side and then MailMate handles it very badly possibly because of an already corrupt state in MailMate, but I'm not sure about that. Let me know if the problem returns and we'll give it another go.

    The Mail vs. Thunderbird import behavior does not seem like it could be related. I guess MailMate won't allow you to import from Mail now which makes it tricky to reproduce (without removing the account again). Do you know if there were any differences between the account settings in Mail and Thunderbird?

    Have you enabled sending crash reports in the General preferences pane? I don't seem to have the import-related crash(es). It could probably tell me where to look for the problem and possibly reproduce it based on one of your preferences files.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket