Freron MailMate

Comments and changes to this ticket

• 

  benny August 10th, 2014 @ 11:26 AM

  Thanks. You can just let MailMate send all crash reports. It helps to see how bad a given problem is.

  I'm very interested in fixing this. Could you try to see if the problem is reproducible somehow?

  Alternatively, how often does it happen for you?

• You flagged this item as spam.
  

  Leo August 10th, 2014 @ 01:52 PM

  I have been sending crash reports for a few months now. Can you find them by email address?

  The crash is reproducible 100% when I'm in the inconsistent state (email shows as unread on iOS device) however, I don't know how it gets into that state.

  This has happened maybe 10 times over the past few months?

• 

  benny August 10th, 2014 @ 02:11 PM

  Yes, I can find the crash reports. I just thought you didn't allow MailMate to send all of them.

  I've checked your 10 most recent crash reports and they are all the exact same issue which makes your estimate very precise :-)

  The first you can do for me is to launch MailMate from a Terminal window like this:

  /Applications/MailMate.app/Contents/MacOS/MailMate
  

  After a crash, the window should contain some output which can help me look in the right direction. After that I might need to add more debug output, but it'll be a good start.

  I would also appreciate if you experimented a bit to see if you can find a series of steps which triggers the problematic state.

  So far, these are the facts:

  • MailMate and the iOS device are both running.
  • You are actively using the iOS device.
  • For some reason, MailMate does not show one or more new messages.
  • Archiving on the iOS device triggers MailMate to crash.

  That last step indicates that MailMate is told that a message was deleted from the Inbox, but maybe somehow MailMate was not aware or only partly aware that it existed at all.

  Do you receive a large number of messages? (I'm thinking the trigger may be rare and related to some kind of race condition.)

  Thanks for your help.

• You flagged this item as spam.
  

  Leo August 10th, 2014 @ 02:42 PM

  I do receive a large number of messages (~150/day with some days in the several hundreds if something goes wrong with our systems).

  Yup, the facts are accurate. I actively clean my inbox and archive messages that I don't need mostly through MailMate. I'm usually not actively using the iOS devices - but once in a while, I'll notice that there are emails on it that show unread - which doesn't correspond to MailMate's state. I don't remember whether the gmail web interface agrees with MailMate or the iOS device but will check it the next time this occurs. When I then archive them on the iOS device, MailMate immediately crashes.

  Anecdotally, these messages have been of low importance (automated warning emails and build failure messages) so I haven't gone back and looked if they showed up in MailMate at some point. Going forward I'll dig into these messages more.

  I'll run it from Terminal and let you know any console output I see.

• You flagged this item as spam.
  

  Leo August 11th, 2014 @ 02:46 AM

  Ok, I'm in a state where I have inconsistent emails again. Gmail web interface agrees with the ios device and not MailMate. See screenshot.

  In MailMate, the message shows up, but only in Archive (which is linked to the gmail All Mail folder) but not in Inbox.

  Here's the console logs since I started MailMate this morning:

  Warning: Sequence number does not exist.  
  Warning: Message copied/added, but destination UID unknown. Deleting message and resynchronizing destination.  
  Warning: A message (630702) was deleted from its destination before it was deleted from its original location  
  Warning: Sequence number does not exist.  
  Warning: Sequence number does not exist.  
  Warning: Sequence number does not exist.  
  Warning: Sequence number does not exist.  
  Warning: Message copied/added, but destination UID unknown. Deleting message and resynchronizing destination.  
  Warning: Sequence number does not exist.  
  Warning: Message copied/added, but destination UID unknown. Deleting message and resynchronizing destination.  
  Warning: Sequence number does not exist.  
  Warning: Message copied/added, but destination UID unknown. Deleting message and resynchronizing destination.  
  Warning: UID 23691 already exists in the destination mailbox (message 0)
  

  When I archive the mail on the ios device, MailMate crashes:

  Fatal: Unexpectedly did not find value 204965  
  update_message_location (6/630702): , 0, imap://leo%40xxxxxx.com@imap.gmail.com/INBOX, 0, 204965  
  Value maps are not identical: $Msgs.filter(#old-source.protocol =[c] 'imap').filter(#old-uid exists)  
  Map (differs from verification map):  
   imap://leo%40xxxxxx.com@imap.gmail.com/INBOX:
    204965: 630702
  Verification map (differs from value map):  
   imap://leo%40xxxxxx.com@imap.gmail.com/INBOX:
  Abort trap: 6
  

  (proper domain replaced with xxxxxx)

  Let me know what else I can provide to help.

• 

  benny August 11th, 2014 @ 01:24 PM

  Thanks for the output. Some of it (decoded text warnings) was a minor output bug which I have now fixed and I cleaned up your output for clarity.

  It is still not clear to me what happens, but it is certainly helpful. One additional question: Could these messages also be moved by a rule in MailMate? (I don't understand how MailMate gets into a state where the messages are only shown on the iOS device.) Any other rules in play? (Gmail filters.)

  Here is another way which might help me: Keep the Activity Viewer open (⌥⌘0) and then use “Help ▸ Send Server Logs” when you see the pre-crash state. Also send the Terminal output like you did in this ticket (in a separate email since you'll have to crash MailMate first).

• You flagged this item as spam.
  

  Leo August 11th, 2014 @ 01:36 PM

  These messages wouldn't be moved by a filter or a rule in either gmail or MailMate.

  You can see from the screenshot before that this message is one of several similar ones that all arrived pretty close together. Is it possible that MailMate considered the one it didn't see in Inbox as a duplicate somehow?

  I'll keep the Activity Viewer open and Send Server Logs the next time it happens.

  It may also be helpful (or it may be a wholly separate bug) that occasionally, when I archive messages on the iOS devices, they don't actually get archived on MailMate and instead show up in the original folder where they were with a red dot next to them.

• 

  benny August 11th, 2014 @ 02:46 PM

  Thanks for the details. Could you also enable this debug variable:

  defaults write com.freron.MailMate MmTrackDatabaseEvents -bool YES
  

  And then also fetch the latest test release: Hold down ⌥ when clicking Check Now.

  Thanks in advance!

• You flagged this item as spam.
  

  Leo August 12th, 2014 @ 12:14 AM

  Just sent Server Logs, crash report and the console dump. Let me know what else I can do. In this case the email wasn't even anywhere in MailMate :-/