Freron MailMate

Comments and changes to this ticket

• You flagged this item as spam.
  

  Chaim Kram October 27th, 2019 @ 05:05 PM

  Another crash, right now (2019-10-27 18:59) — see 2nd attachment

  • mailmate_sample2.txt 108.7 KB

• You flagged this item as spam.
  

  Chaim Kram November 3rd, 2019 @ 10:37 AM

  And another crash... This time on Version 1.13 (5662)

• You flagged this item as spam.
  

  Robert Brenstein November 3rd, 2019 @ 03:58 PM

  Last version in 12 series was really stable for me. No crashes whatsoever. The public release of 13 started crashing but only sporadically. The beta I got to deal with printing crashes more often. My wife got a newer beta and that crashes even more. Some instability creeped in for sure.

• You flagged this item as spam.
  

  Chaim Kram November 13th, 2019 @ 05:56 AM

  Hi Benny,

  Another crash (attached). Can you provide an update on what might be causing this, and how I can fix it? Thanks.

• 

  benny November 13th, 2019 @ 04:10 PM

  @Chaim: I assume you don't have some way to reproduce this?

  Are you using the experimental new message view (which is likely still unstable):

  defaults read com.freron.MailMate MmNewMessageViewEnabled
  

  @Robert: Are you also seeing hangs or do you get actual crashes? You are welcome to send me a few crash reports directly (Help > Send Feedback).

  Major changes were involved in getting MailMate ready for Catalina and although these changes helped fix various issues on Catalina (and will also help with fixing other issues in the future), it has also caused some new issues. I'm sorry about that. My goal is to get MailMate 13.1 ready for release, but what you report here is certainly one of the issues I need to resolve before doing that.

• You flagged this item as spam.
  

  Chaim Kram December 25th, 2019 @ 04:42 PM

  Hi Benny,

  To answer your (much earlier!) questions:

  1. I am not using the MmNewMessageViewEnabled MailMate setting ("does not exist").
     
  2. The crashes now mainly occur when I get on the train, which is to say, when I have poor or inconsistent Internet connectivity. If you can simulate those conditions, I wonder if you can replicate the bug.

  HTH.

  p.s. I was going to attach the latest crash log, but apparently you've reached your upload quota...

• 

  benny January 7th, 2020 @ 06:04 PM

  @Chaim: Could you send me the crash report using “Help > Send Feedback”?

• You flagged this item as spam.
  

  Chaim Kram January 8th, 2020 @ 10:02 PM

  sent crash report as requested

• 

  benny January 9th, 2020 @ 09:10 AM

  I fixed some more issues in the latest test release, but I don't think it's related to this issue unless you are a frequent user of Quick Look. Nevertheless, try it out: Hold down the option key when clicking “Check Now” in the Software Update preferences pane.

  The hang is not a busy-loop issue. It's a locking issue, that is, all threads are waiting for something else to “finish”. This can be very hard to debug without me being able to reproduce it. Let me know if you spot other triggers than a bad internet connection (which I'll emulate while working today to see if anything happens).

• You flagged this item as spam.
  

  Chaim Kram January 13th, 2020 @ 07:29 PM

  Hi Benny,

  Good news: As of the last couple of weeks, I have not suffered any more crashes. I still get the spinning beachball from time to time -- replying to messages occasionally does it -- but it always seems to recover after a few seconds.

  Indeed, the crash report I sent you seems to be the last crash I suffered. I am hopeful that one or several of the fixes you've made in the recent versions has done the trick.

  I'll update you if I see another crash. Anyway, thanks for your responsiveness to this, I do appreciate it!

• 

  benny January 14th, 2020 @ 07:16 AM

  • State changed from “new” to “cantreproduce”

  Thanks for the update. Based on a crash report I got from someone else then I'm not 100% sure this is fully fixed -- or at least only partially fixed. I'll mark it as “cantreproduce” for now. You can still add comments should the issue return.