#1092 ✓cantreproduce
Andrew Webb

Mailmate Crashes 10 secs after launch [r5086 and latest standard 1.91 release]

Reported by Andrew Webb | April 4th, 2015 @ 07:05 PM

First of all, thanks for such a great application. I'm a very satisfied customer.

After this latest update, MailMate quits about 10 seconds after launching, whether I'm connected to the Internet or not.

MacBook Pro (17-inch, Mid 2010)
2.66 GHz Intel Core i7
8 GB 1067 MHz DDR3
Yosemite 10.10.2 (14C1514)

Here's what I've tried:

Repaired permissions and restarted
Launched both on and offline (same results)
Downloaded and tried r5086 (same results)

Launched from terminal. Dump from terminal and Apple Crash Report are here: http://files.webbtransfer.com/text/371c3P3i411v

Tried Database rebuild http://manual.mailmate-app.com/rebuild
[rm ~/Library/Application\ Support/MailMate/*.tmp] No such file or directory [~/Library/Application\ Support/MailMate/.rebuild.tmp] Permission denied

Here's a screenshot of ~/Library/Application\ Support/MailMate: http://files.webbtransfer.com/image/1R1S381a371U

Anything else I can do to help solve this problem?



Comments and changes to this ticket

  • benny

    benny April 4th, 2015 @ 07:32 PM

    • State changed from “new” to “cantreproduce”

    Sorry about your trouble. If I understand correctly then r5084 was the one originally crashing. (The r5086 is very cutting edge and shouldn't really be used in general, but I don't think that is the issue here.)

    I'm afraid you have tried so many things that there might not be a lot to debug. I suggest letting MailMate refetch and index all emails. You can do it by deleting the following folders:

    ~/Library/Application Support/MailMate/Database.noindex
    ~/Library/Application Support/MailMate/Attachments
    ~/Library/Application Support/MailMate/Messages

    And also any .tmp files as you have also done previously. That should give you a clean start and I hope you don't have a huge email collection to refetch. If the problem returns then let me know before you try rebuilding. That might make it easier to figure out what went wrong.

  • benny

    benny April 4th, 2015 @ 09:51 PM

    Hmm, that does look weird. Are there any problems with your disk?

    There should be a bit more information if you launch from a Terminal window and then make MailMate crash:

  • benny

    benny April 5th, 2015 @ 06:27 AM

    Hmm, it seems MailMate think the app support folder is empty and therefore tries to delete it. Have you tried sym-linking/aliasing any folders to a different location?

    SpamSieve is not launched before it is needed (arrival of messages).

    For now, let's assume the problem with smart mailboxes is related to the main problem.

  • benny

    benny April 5th, 2015 @ 06:31 AM

    Hmm, it might be permissions related. What does this return:

    ls -ld ~/Library/Application\ Support/MailMate
  • benny

    benny April 6th, 2015 @ 07:26 AM

    That's different than mine:

    drwxr-xr-x  23 benny  staff  782 Apr  6 09:10 /Users/benny/Library/Application Support/MailMate

    In any case, MailMate shouldn't crash and I'll look into that. You can get permissions like mine using this

    chmod a+rx ~/Library/Application\ Support/MailMate

    but the real problem might be the + which means there are extended attributes. I think they can be listed like this:

    ls -lde ~/Library/Application\ Support/MailMate

    I'm not an expert in these issues, but it would be interesting to see the output (still, the real problem is that MailMate crashes). If you want to try removing the extended attributes on the folder then it can be done like this:

    chmod -N ~/Library/Application\ Support/MailMate

    Note that I don't know why it's there and whether it could somehow be important.

  • benny

    benny April 7th, 2015 @ 07:56 PM

    @Rodney: Doesn't seem like it is the same issue. Have you allowed MailMate to send crash reports (see the General preferences pane)? I don't seem to be able to locate anything with the name rodney.

  • benny

    benny April 8th, 2015 @ 09:15 AM

    @Andrew: It's probably related, but it's not the same issue. In this case renaming a file unexpectedly fails. If you were running MailMate from a Terminal window then you should see a more detailed error (which file was renamed). Alternatively, you might find it here:

    grep MailMate /var/log/system.log
  • benny

    benny April 8th, 2015 @ 09:16 AM

    @Rodney: Ok, let me know if it happens again.

  • benny

    benny April 10th, 2015 @ 06:50 AM

    @Matt: Ok, I think you can crash MailMate by doing any change which requires updating one of the main .plist files. For example, changing IMAP settings, signatures, tags, or smart mailboxes. MailMate is not even allowed to rename files in the main folder:

    ~/Library/Application Support/MailMate/

    In other words, there is still some kind of problem with the folder/file permissions. Could you investigate?

    (I cannot work around an error when renaming a file.)

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