Freron MailMate

Comments and changes to this ticket

• 

  benny July 3rd, 2017 @ 06:26 PM

  I believe the problem is likely to be a specific email within that account. It'll be tricky for you to figure out which one, but you can probably narrow it down to a single mailbox within the account (by taking all mailboxes offline and then take them online one by one until MailMate crashes).

  If I'm right that it's the parsing of a message that crashes MailMate then we can get a copy of the email like this. Open a Terminal window and then issue this command:

  defaults write com.freron.MailMate MmDebugFetchCrash -bool YES
  

  Launch MailMate and wait for it to crash. Then try this command to see if something has been saved:

  ls /tmp/*.eml
  

  (This debug variable exists because of a similar issue long ago.)

  Let me know what you find. I'm naturally very interested in figuring out what the issue is.

• 

  benny July 3rd, 2017 @ 06:27 PM

  In order to disable the debug variable:

  defaults delete com.freron.MailMate MmDebugFetchCrash
  

• You flagged this item as spam.
  

  Christophe Simonis July 3rd, 2017 @ 06:44 PM

  No luck :(

  [chs:~/] $ ls /tmp/*.eml                                                                                                                                                       20:41
  fish: No matches for wildcard '/tmp/*.eml'. See `help expand`.
  ls /tmp/*.eml
     ^
  [chs:~/]¬124 $ defaults write com.freron.MailMate MmDebugFetchCrash -bool YES                                                                                                  20:41
  [chs:~/] $ /Applications/MailMate.app/Contents/MacOS/MailMate                                                                                                                  20:42
  2017-07-03 20:42:29.368 MailMate[71652:380212] Bartender: Loaded BartenderHelperTwoOneThree
  fish: '/Applications/MailMate.app/Cont…' terminated by signal SIGBUS (Misaligned address error)
  [chs:~/]¬138 $ ls /tmp/*.eml                                                                                                                                               26s 297ms
  fish: No matches for wildcard '/tmp/*.eml'. See `help expand`.
  ls /tmp/*.eml
     ^
  [chs:~/]¬124 $
  

• 

  benny July 3rd, 2017 @ 07:12 PM

  Thanks for trying. I'm not sure why that didn't work, but I'll take a look at the code which seems to be related to the crash reports. Maybe I can spot what could trigger a crash.

  You can try the latest test release just to make sure it's not a fixed issue (I don't think it is).

• 

  benny July 3rd, 2017 @ 07:26 PM

  Ok, here's another release. Before launching it then enable this debug variable:

  defaults write com.freron.MailMate MmDebugMergeCrash -bool YES
  

  Launch from a Terminal window and there should be a lot of output. I'm mostly interested in some of the last lines I believe.

• 

  benny July 3rd, 2017 @ 07:27 PM

  Sorry wrong link. Here we go.

• You flagged this item as spam.
  

  Christophe Simonis July 3rd, 2017 @ 09:51 PM

  Wow! A personal build!

  Indeed, there is a lot of output (44M, non attached as it may contains sensible data).
  The important part seems to be logged to file /tmp/mailmate_logs/mailmate_parser_problems.log (see attachment)

  • mailmate_parser_problems.log 1 KB
• 

  benny July 4th, 2017 @ 11:02 AM

  It's actually the other data I'm interested in. Not all of it, but maybe a few hundreds of the final lines. I'm looking for a string which I think causes part of my code to go into an infinite loop. These lines start with Merge.

  You can send it to me privately if the content is sensitive in any way.

  Thanks in advance.

• 

  benny July 4th, 2017 @ 09:45 PM

  • State changed from “new” to “fixcommitted”

  Try this test release.

  The email triggering this is really weird, but it exists and therefore MailMate should be able to handle it. Let me know whether or not it works now.

• You flagged this item as spam.
  

  Christophe Simonis July 4th, 2017 @ 10:04 PM

  Thank you.
  The bug has been fixed. I can finally read my emails.

• 

  benny September 22nd, 2017 @ 12:54 PM

  • State changed from “fixcommitted” to “fixreleased”

  [bulk edit]