Freron MailMate

Comments and changes to this ticket

• 

  benny March 29th, 2012 @ 10:04 AM

  • State changed from “new” to “reproduced”

  This is probably two separate problems. I receive very few crash reports, so I think I have identified some of your crash reports (those sent by MailMate if allowed) and I think I can reproduce and fix the second problem (quickly viewing a message after arrival).

  The “Save as...” crash is more difficult. Maybe you can send me a crash report related to this issue or just tell me right after it
  happened and you restarted MailMate (I can then locate the crash report sent by MailMate).

  I'll mark the ticket as reproduced to track progress on the first issue.

• 

  benny March 29th, 2012 @ 10:43 AM

  Turns out I couldn't reproduce the crash, but based on the crash report I have attempted to fix the problem. Any additional information about both problems would be appreciated.

• You flagged this item as spam.
  

  Christian Behrens March 29th, 2012 @ 11:05 AM

  Thanks for the quick reaction. I attached the crash report for the use case "Ctrl-click on inline-attached image and select 'Saving As' ". Hope this helps.

  Process:         MailMate [9721]
  Path:            /Applications/MailMate.app/Contents/MacOS/MailMate
  Identifier:      com.freron.MailMate
  Version:         1.4.2 (2818)
  Code Type:       X86 (Native)
  Parent Process:  launchd [1909]
  
  Date/Time:       2012-03-29 12:55:34.066 +0200
  OS Version:      Mac OS X 10.7.3 (11D50)
  Report Version:  9
  
  Interval Since Last Report:          355736 sec
  Crashes Since Last Report:           27
  Per-App Interval Since Last Report:  28684 sec
  Per-App Crashes Since Last Report:   18
  Anonymous UUID:                      B997A522-E135-4B69-9FFC-F20D687965F1
  
  Crashed Thread:  0  Dispatch queue: com.apple.main-thread
  
  Exception Type:  EXC_BAD_ACCESS (SIGBUS)
  Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000fefff000
  
  VM Regions Near 0xfefff000:
      CG backing stores      00000000c7e1b000-00000000c7ee1000 [  792K] rw-/rw- SM=SHM  
  --> VM_ALLOCATE            00000000fefff000-00000000ff000000 [    4K] rw-/rwx SM=COW  
      Submap                 00000000ffff0000-00000000ffff2000          r-x/r-x process-only submap
  
  Application Specific Information:
  objc[9721]: garbage collection is OFF
  
  Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
  0   ???                             0xfefff000 0 + 4278185984
  1   com.macromates.MailMate.OakAppKit   0x00202416 0x1ff000 + 13334
  2   com.macromates.MailMate.OakAppKit   0x002157ae 0x1ff000 + 92078
  3   com.freron.MailMate             0x00085d3c 0x1000 + 544060
  4   com.apple.AppKit                0x9737d036 -[NSMenu _populateFromDelegateWithEventRef:] + 318
  5   com.apple.AppKit                0x9726be7f -[NSMenu _populateWithEventRef:] + 99
  6   com.apple.AppKit                0x9737c179 -[NSCarbonMenuImpl _carbonPopulateEvent:handlerCallRef:] + 448
  7   com.apple.AppKit                0x9737bd02 NSSLMMenuEventHandler + 452
  8   com.apple.HIToolbox             0x926e162c _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
  9   com.apple.HIToolbox             0x9255cf4f _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1602
  10  com.apple.HIToolbox             0x9255c3cc _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 482
  11  com.apple.HIToolbox             0x9255c1e4 SendEventToEventTargetWithOptions + 75
  12  com.apple.HIToolbox             0x9272a96c SendMenuPopulate(MenuData*, OpaqueEventTargetRef*, unsigned long, double, unsigned long, OpaqueEventRef*, unsigned char*) + 370
  13  com.apple.HIToolbox             0x927350ed _ZL15SendMenuOpeningP14MenuSelectDataP8MenuDatadmmP14__CFDictionaryhPh + 300
  14  com.apple.HIToolbox             0x9273967c _ZL11DrawTheMenuP14MenuSelectDataPP9__CFArrayhPh + 202
  15  com.apple.HIToolbox             0x9273a6bf OpenSubmenu(MenuSelectData*, MenuData*, unsigned char, unsigned char*) + 218
  16  com.apple.HIToolbox             0x925a9407 _ZL15TrackMenuCommonR14MenuSelectDataPh + 1597
  17  com.apple.HIToolbox             0x9273c382 _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttmS4_S4_PK10__CFStringPP13OpaqueMenuRefPt + 1782
  18  com.apple.HIToolbox             0x9273c6c4 _HandlePopUpMenuSelection7 + 639
  19  com.apple.AppKit                0x9755028a _NSSLMPopUpCarbonMenu3 + 4532
  20  com.apple.AppKit                0x9754dd6b -[NSCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 210
  21  com.apple.AppKit                0x976e0aa2 -[NSMenu _popUpContextMenu:withEvent:forView:withFont:] + 294
  22  com.apple.AppKit                0x976e0977 -[NSMenu _popUpContextMenu:withEvent:forView:] + 62
  23  com.apple.AppKit                0x976e0b8e -[NSMenu _popUpMenuWithEvent:forView:] + 51
  24  com.apple.AppKit                0x972d9c62 -[NSWindow sendEvent:] + 7466
  25  com.apple.AppKit                0x972720e7 -[NSApplication sendEvent:] + 4788
  26  com.apple.AppKit                0x972036d5 -[NSApplication run] + 1007
  27  com.apple.AppKit                0x97497261 NSApplicationMain + 1054
  28  com.freron.MailMate             0x00017778 0x1000 + 92024
  29  com.freron.MailMate             0x00003385 0x1000 + 9093
  

  (Edited by Benny to shorten it and make it more readable.)

• 

  benny March 29th, 2012 @ 12:50 PM

  It seems the crash is related to the “Open With” menu item. Can you confirm that?

  Unfortunately I cannot reproduce this crash either.

• You flagged this item as spam.
  

  Christian Behrens March 29th, 2012 @ 01:08 PM

  Yes, that is correct. The application freezes and subsequently crashes while attempting to either display the second-level context menu of "Open With", or while trying to open the file system dialog window following a click on "Save As.."

• 

  benny March 29th, 2012 @ 02:09 PM

  • State changed from “reproduced” to “cantreproduce”

  The crash following a click on “Save as...” should result in a different crash report. Could you enable sending crash reports in the Preferences and let me have both variants. I don't really think they have anything in common, so I'm kind of lost right now.

  I forgot that you wrote “certain types of attachments”. Any pattern to that?

  If possible, could you try running MailMate in a separate account on the same machine?

  Maybe even try to save/open one of these attachments in MailMate on a different machine?

  (I've changed the state of the ticket, but it does not mean I have given up.)

• You flagged this item as spam.
  

  Christian Behrens March 29th, 2012 @ 02:47 PM

  I attached the crash reports for both use cases ("Save Attachment" and "Open With.."). Seems as if it chokes up on any kind of image attachment.

  I tried running it under a different account on this machine, with the same error happening. On a different machine running Snow Leopard everything works fine, though.

  To make a clean reinstall, are there any resources to remove other than MailMate.app and the MailMate preferences folder?

  • errorlog_open_with.txt 59.9 KB
  • errorlog_save_attachment.txt 68.5 KB
• 

  benny March 29th, 2012 @ 03:13 PM

  Thanks for crash reports. I'll examine them later.

  Deleting the following files should reset everything, but I don't think you should do that (a different account would also have the same effect):

  ~/Library/Application Support/MailMate
  ~/Library/Preferences/com.freron.MailMate.plist
  

  I think the problem may be related to something you have installed. Maybe something handling the attachment type. Although that does not really explain why “Save Attachment” crashes...

• 

  benny March 30th, 2012 @ 08:17 AM

  I've looked into the crash reports and I still see no common theme, but I would like to rule out some external factors. The crash reports show:

  0x83ee000 -  0x8408fff +AdobeBIB (??? - ???) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBIB
  0x8413000 -  0x8417ff7 +org.tigris.scfinderplugin (??? - 169) <BBADB6CA-61AE-24D5-4E0A-EBCCAD3F0D92> /Library/Contextual Menu Items/SCFinderPlugin.plugin/Contents/MacOS/SCFinderPlugin
  0xac00000 -  0xac3cfc7 +com.adobe.vcmenu (??? - 4.0.0.344) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/MacOS/ADFSMenu
  

  In other words you have some plugins related to context sensitive menus. Could you try to disable them, i.e., move anything located in /Library/Contextual Menu Items/ and then restart MailMate. (For the record, on my system this folder is empty.)

• You flagged this item as spam.
  

  Christian Behrens March 30th, 2012 @ 09:49 AM

  Awesome. That did it.

  I had a plugin called SCPlugin in /Library/Contextual Menu Items, which apparently gets installed along with http://scplugin.tigris.org (which I haven't actually used in ages and which only seems to cause trouble after upgrading from SL to Lion). As far as I can gather from googling about the plugin, it seems to cause crashes in a bunch of other applications as well, e.g. Evernote.

  Removed the plugin and MM works like a charm again. Thanks a lot and keep up the good work!

• 

  benny March 30th, 2012 @ 01:13 PM

  • State changed from “cantreproduce” to “resolved”

  Good. I'm just not sure it also fixed the other crash type you had
  (quickly selecting an incoming message). Let me know if that happens again.

  [state:resolved]

• You flagged this item as spam.
  

  Michael Young March 30th, 2012 @ 02:41 PM

  Based on the clue above I checked my Contextual Menu Items folder. I also had an old item called SCFinderPlugin. I have no idea when or where I first got it (it has a 2007 date). I have removed it and will watch for further crashes (I hope there aren't any).

  MailMate has not crashed on my Air, which never saw this plugin. Maybe that is it...

• You flagged this item as spam.
  

  Christian Behrens March 30th, 2012 @ 02:53 PM

  I actually had two plugins in my Contextual Menu Items folder: SCFinderPlugin mentioned above, and a plugin called ADFSMenu. The former is part of the Subversion client for Mac (http://subversion.tigris.org/), the latter one belongs to a service called Adobe Drive CS4, which I never used and which I've got hardly any knowledge about. Obviously these plugins are used to extend the standard context menus in OSX by additional services, e.g. in the case of the Subversion client I remember several standard SVN commands being integrated into the context menu for Finder items. My suspicion is that with the upgrade to OSX Lion these custom context menus cause trouble because the underlying UI structure of the context menus has somewhat changed? Just an idea, but it would go well with the fact I didn't have any of these problems with earlier versions of OSX.

• 

  benny March 30th, 2012 @ 02:59 PM

  Thanks for the updates.

  Maybe one of you could send me the plugin such that I can test myself if is related to the crash type that you both saw (I'm still not convinced about that). This is the “click on a message that just arrived in my inbox” type of crash.

• You flagged this item as spam.
  

  Christian Behrens March 30th, 2012 @ 03:03 PM

  • no changes were found...
• 

  benny January 13th, 2013 @ 03:29 PM

  For future reference: Any crashes in setRepresentedURL are most likely also caused by SCFinderPlugin. (And this kind of crash could be triggered when simply selecting a message.)