#2328 new
Daniel Willitzer

Application Crash Afterup upgrade Version 1.12.5 rv 5635

Reported by Daniel Willitzer | May 27th, 2019 @ 09:51 PM

Unable to determine the cause of application freeze immediately after launching.

Errors (found in the console.app):

  1. Attempting to perform block on main runloop, but the main thread as exited. This message will only log once. Break on _CFRunLoopError_MainThreadHasExited to debug.

  2. Attempting to wake up main runloop, but the main thread as exited. This message will only log once. Break on _CFRunLoopError_MainThreadHasExited to debug.

Here is the (GIST)hang diagnostic report.

Please advise?

Comments and changes to this ticket

  • Daniel Willitzer

    Daniel Willitzer May 27th, 2019 @ 10:36 PM

    ✅ ::RESOLVED:: Found after purging files in /Users/User/Library/Application Support/MailMate/Cache Mailmate re-imported all messages and no longer having the hang/freezing issue mentioned.

    Will update ticket if happens again within the same build.

  • Ayhan

    Ayhan May 29th, 2019 @ 12:44 PM

    I have the same problem; reproducable on both High-Sierra and Mojave.

    When it occurred a couple days ago, I was still on High-Sierra. At the time, the logs hinted at an issue with code signing and keychain access.

    Lucikly, I was able to pull the previous MM version from backup and get my email going again with that copy (i.e. Mailmate Version 1.12.4 [5594]). restoring just the application bundle (MailMate.app) was sufficient, without any need to restore user data.

    Meanwhile I migrated to Mojave, which went quite smoothly; that restored MailMate.app was still working after the OS migration.

    And then, earlier today, MailMate popped the upgrade dialog again; So I went ahead and gave it another chance for installing the new MM version (1.12.5 rv 5635), hoping that the migration to Mojave might have helped... But nope... Same thing again.... So no I am back to the restored copy of "MailMate.app"...

    I am afraid deleting the MM mail cache may not be a preferable option for me, since I am managing quite a few email acoounts (around 20), with a gzillian old mails on most of them. What's worse is that some of those mails may no longer be on the server...

  • benny

    benny May 31st, 2019 @ 09:36 AM

    Sorry about the late response.

    @Ayhan: Please don't delete your cache until after we have tried to determine what causes this to happen. When this happens, could you try and run the following command and send me the result:

    sample MailMate 10 > ~/Desktop/mailmate_sample.txt
  • Ayhan

    Ayhan June 2nd, 2019 @ 12:11 AM

    Hi Benny,

    Thank you for your response.

    My apologies for the late response on my end as well. I was travelling for a couple days.

    I have just sent the requested sample (as well as some extra material) via the the MM feedback route.


  • Ayhan

    Ayhan June 9th, 2019 @ 01:02 AM

    Hi Benny,

    Any news on this one?

    BTW, you did get the second batch of files (Mailboxes.plist and timed outputs) that I have sent over the feedback channel, right?


  • Ayhan

    Ayhan July 11th, 2019 @ 03:16 PM

    Notes to future self and others who have the same issue (as Benny appears to be busy...)

    Today, I have spent some more time on this after accidentally clicking ok for the application update dialog.

    • 0) Took a backup of my MailMate data folder (/Users/User/Library/Application\ Support/MailMate)

    • 1) Then, I tried following the Daniel Willitzer's suggestion above, but deleting the Cache folder (/Users/User/Library/Application\ Support/MailMate/Cache) did NOT help or even change anything in my case. It just resulted in MailMate (v1.12.5) regenerating the two plist files that were preveiously in there (it did not attempt to download anything).

    • 2) Next, I switched back to previous MailMate release, v1.12.4 [5594] and took all my IMAP accounts offline; quit the application and re-deleted the Cache folder.

    • 3) Relaunched the new version of MailMate (v1.12.5)

    In the end, the attempt was still unsuccessfull, BUT with a different outcome than the previous attempts:

    • a) With the accounts online, the MailMate app (v1.12.5) would hang before fully displaying its windows (only the window borders were visible)
    • b) This time, MM was able to display its main window after starting up, and then, for a couple seconds, I was even able to click on mailboxes and view some message lists until the window display froze again.

    Note that in both cases (a & b), after startup phase is completed, I am able to interact with MM's menus (and trigger related actions); but in the end, it's the window display that malfunctions.

    FYI, the startup phase deos take a while (up to a minute) and consumes high CPU, but that was already the case when things were working. Once that phase is over, MailMate goes to a low CPU consumption state, as expected.

    When MM hangs, it doesn't look like it is stuck in a loop. Quite the contrary: At that stage, it has got very low CPU consumption and no access to disk/network.

    It's almost as if it's waiting for something (such as a user response), but then again, there are no visible dialogs...

    For now, I am going back to MM v1.12.4 [5594].

  • benny

    benny August 1st, 2019 @ 07:42 AM

    Thanks for your patience! I've sent a reply to the information you sent me via direct email.

  • olivernoah41 (at gmail)

    olivernoah41 (at gmail) September 16th, 2019 @ 06:55 AM

    I am very glad to be here. I am very happy to see this post. Mr Daniel Willitzer i want to appreciate you and your post. Best Place To Get Industrial Shelving

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