Pressing Reply will result in a beachball.

Thanks for the report. I haven't seen any crash reports I believe. Have you enabled sending crash reports in the General preferences pane? (I don't get those sent to Apple.)

It looks like an infinite loop and I think it's somehow related to your reply settings. What is your “Reply:” setting in the Composer preferences pane?

Here is a direct link to the previous public release.

Hi Benny,

The app didn't crash, but I did a forced quit. (The send crash reports under general are on.) Happy to send some traces, but please let me know what you need. (Maybe a kill signal or the likes on the main process?) I can't attach a screenshot of the composer setting due to "Upload quota reached". But I have the following:
- New Message default account: SJC (which is an active account) - Reply: when pressing cmd-r: ask for reply type - Only include selected text unchecked - Markdown: Enable composer menu: unchecked - Attachment check: enabled - default in pattern iirc - sent message sound: none

Thx,
Stijn

I'm seeing something possibly related -- simply selecting a message in the Inbox causes MailMate to hang, requiring a Force Quit. Here's the beginning of the report:

Date/Time: 2015-10-02 06:13:54 -0400
OS Version: Mac OS X 10.11 (Build 15A284)
Architecture: x86_64
Report Version: 22

Command: MailMate
Path: /Applications/MailMate.app/Contents/MacOS/MailMate
Version: 1.9.2 (5141)
Parent: launchd [1]
PID: 7287

Event: hang
Duration: 8.20s (process was unresponsive for 181 seconds before sampling)
Steps: 82 (100ms sampling interval)

Hardware model: MacBookPro10,1
Active cpus: 8

Fan speed: 2158 rpm

(Follow-on to previous)

I should have noted that not every message in the Inbox causes this behavior.

@Steve: Could you send me a full hang report using “Help ▸ Send Feedback” (if possible)? Does it work for you with the previous public release (link is in my first reply in this ticket).

@Stijn: I think I'll have to make a debug release to learn more about what happens in your case. I assume it happens no matter which email you reply to? Does it still work with the previous public release?

I just sent the requested crash report. As further information about the hang, I've read and deleted the problem messages (using an inferior mail client :-), but attempting to read them in the Deleted Messages collection results in the same hang -- that's what caused the hang in the crash report I mailed you. I get the same behavior with the previous public release, so I suspect this is due to my upgrade to El Capitan yesterday. I've got another, not-yet-upgraded machine, and will check the behavior there and report back.

Just checked on a not-yet-upgraded-to-El Capitan machine; no problem opening the afflicted messages with 1.9.2.

@Steve: Could you “Message ▸ Forward as Attachment” one of these messages to me and then I'll test on El Capitan?

Hi Benny,

For some reason my previous comment was not recorded (Maybe too long with the sampled process info included). But I tried with both Version 1.9.2 (5141) and r5084. For r5141 hitting reply to both html and plaintext results in a beachball with no compose window even opening. For r5084 on the same messages I get an compose window as expected.

Could it maybe have to do with PGP as well? I have a process sample made in activity monitor. But the last time I pasted it below it didn't record the feedback. What I see is the following:

Sampling process 20738 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling MailMate (pid 20738) every 1 millisecond
Process: MailMate [20738]
Path: /Applications/MailMate.app/Contents/MacOS/MailMate
Load Address: 0x102673000
Identifier: com.freron.MailMate
Version: 1.9.2 (5141)
Code Type: X86-64
Parent Process: ??? [1]

Date/Time: 2015-10-02 15:43:44.790 +0200
OS Version: Mac OS X 10.10.5 (14F27)
Report Version: 7

Analysis Tool: /usr/bin/sample

Call graph:
2445 Thread_418252 DispatchQueue_1: com.apple.main-thread (serial) + 2445 start (in MailMate) + 52 [0x102674d74] + 2445 main (in MailMate) + 552 [0x10268d11b] <>
+ 1160 header::address_name_and_email_function(char const*&, char const*) (in OakMIME) + 1227 [0x102e06873] + ! 1160 _platform_memchr$VARIANT$Haswell (in libsystem_platform.dylib) + 38,63,... [0x7fff90698c26,0x7fff90698c3f,...] + 1160 header::address_name_and_email_function(char const*&, char const*) (in OakMIME) + 1206,676,... [0x102e0685e,0x102e0664c,...] + 125 DYLD-STUB$$memchr (in OakMIME) + 0 [0x102e355a0]

I see OakMime, maybe related to that?

But happy to run other traces/debug tools or the likes if you want.

Stijn

I've forwarded one of the "bad" messages.

Hi Benny,

I upgraded to ElCap in the meantime and the symptoms on the r5141 are identical. I also changed my GPG config to remove the options:
#keyserver-options auto-key-retrieve #auto-key-locate local keyserver

This didn't seem to make a difference either. Based on this maybe the debug build you referred to earlier is a good option. When you have time to create this please let me know and I'll retry with this. Feel free to provide the details outside of this to me if you want to keep the debug build to a limited distribution.

Stijn Jonker
sjcjonker@sjc.nl

Hi Benny,

Anything I can do here?

Stijn

@Stijn: Sorry, one of you comments went into the Lighthouse spam filter. I've been (quite a bit) slow on this ticket. Did I get a full sample from you via email? I don't seem to be able to find it. Use “Help ▸ Send Feedback” to send it.

@Steve: I did get your samples and I'll take a look at them now.

@Steve: It doesn't appear to hang when replying. It appears to hang when selecting a message in the messages outline. When this happens then MailMate generates HTML to be displayed in the message view, but it hangs when writing data to the script converting plain text to HTML. Do you think you have any customizations which might affect this?

Lighthouse rejected my email reply, so here's what I sent:

Is this a MailMate-supplied script, or a system-supplied one? Although I'm now retired, my machine used to be used as a development box, so it's possible there's something in my path screwing things up. What's the name of the script? I'll see what I can find.

Also, you're correct that the hang isn't replying, it's just selecting a message in the outline (as I had tried to make clear in my initial comment on October 2).

@Steve: Your issue has also been reported by another user. Could you write to me via “Help ▸ Send Feedback” and I'll keep you up to date on this issue. The script is provided by MailMate, but I don't think the issue is the script itself. Also given that it does appear to work to select some messages (triggering the same script) before it fails.

@Stijn: I'll get back to you when I have time. We'll track your issue in this ticket and I'll handle @Steve by email. I don't think the issues are related.

Thanks for your patience.

@Stijn: Could you quit MailMate and then try the following in a Terminal window:

defaults write com.freron.MailMate MmDebugAddressParserCrash -bool YES
/Applications/MailMate.app/Contents/MacOS/MailMate

Trigger the hang and then send me the output in the Terminal window.

I couldn't reproduce the issue with the example messages I received from you (more than a week ago), but now that I think about it then the issue could be your configured identities. Try sending me this file as well:

~/Library/Application Support/MailMate/Identitites.plist

Thanks in advance!

Hi Benny,

No rush, as the previous version still works for me. I hope you don't mind if I send the info via email instead of dumping all the contacts in the ticket (as attachment, I assume they are world readable). It should be with you in a few minutes.

Thx,
Stijn

Beginning this morning I see a similar issue here: a few messages will cause Mailmate to hang when I try to open them. I do not see a pattern in the type of messages that cause the issue and with at least one of the messages I'm sure that I was able to read it when it arrived.

Whant can I do to help in debugging?

@mariow: You could fetch this test version and then try what I described above:

defaults write com.freron.MailMate MmDebugAddressParserCrash -bool YES  
/Applications/MailMate.app/Contents/MacOS/MailMate

This is under the assumption that it's the same problem as seen by Stijn. You can send the output using email. Note that there is probably a lot of output, but I only need the last ~100 lines.

Thanks in advance.

@mariow: Try this test release.

Benny, you should have an email with the log from me on the feedback email address. I'm afraid it does not help much.

What I also tried is disabling all bundles, disabling Spamsieve and disabling OpenPGP. None of this made any difference.