[quote user="PhilipAL"]Okay, I have twice managed to cause Pegasus to terminate abnormally this morning. I have assumed that the MiniDump process is always running, but it appears not to have caught anything.[/quote]

It might be required to use MiniDump's "stand-alone" mode where it monitors Pegasus Mail as a child process (see MiniDump's ReadMe for details).

[quote user="PhilipAL"]The trick to cause Pegasus to terminate abnormally is to wait a couple of seconds between selecting "End check" and "Cancel".[/quote]

Since it's apparently reproducable I should be able to create a dump myself or David Harris can recreate it from within his VC debugger.

[quote user="PhilipAL"]It's up to you whether you deem it worthwhile to pursue this problem.[/quote]

It's up to David Harris ...

With reference to a separate related message posted to the Suggestions forum, I have experienced the following problems with the new multi-language spell checker.

I have been unable to find any method of aborting the spell check process once the "Start check" button has been selected.  The only option is to "End check", which results in sending of the message.

In an effort to bail out of the check process, I selected "End check", followed immediately by "Cancel" in the message window.  The result was:

 - the message transmission process began, as shown by the info bar at the bottom of the Pegasus window;

- the message appeared in the "copies to self" folder but without the original message body data. Instead there appears the statement "No formatted contents: Please try to follow link to display plain text, if any", which of course there isn't.

- the Pegasus client crashed.

- the embarrassing thing is that the complete message contents do actually get sent to the recipient.

[quote user="PhilipAL"]I have been unable to find any method of aborting the spell check process once the "Start check" button has been selected.  The only option is to "End check", which results in sending of the message.[/quote]  

See this post/thread. And with regard to the crash: Just don't do it. But if you want to provide a detailed report see item 3 in the crash/hang post and submit a crash dump.

Thank you for pointing to the previous thread on this subject which I had not found.  I have understood that the "Don't send" button functionality as it used to be will be returning soon.

With reference to the crash which I experienced previously, I will follow your advice to "don't do it" under normal circumstances. As recommended, I have downloaded and installed the MiniDump extension and have attempted to recreate the crash without success as yet.

 What I still find to be inappropriate operation is that a message will be sent after selecting "End check", even if one attempts to discard the message as follows:

Okay, I have twice managed to cause Pegasus to terminate abnormally this morning. I have assumed that the MiniDump process is always running, but it appears not to have caught anything.

The trick to cause Pegasus to terminate abnormally is to wait a couple of seconds between selecting "End check" and "Cancel".  Once "Cancel" has been selected, progress of the message transmission process shown in the status window at the bottom left hand corner of the Pegasus window is halted until after answering the "Are you sure that you want to discard message" prompt.  After answering this prompt, and it doesn't matter whether it is answered by "Yes" or "No", the message transmission process completes and Pegasus exits.  When Pegasus is re-started, it indicates that there was an abnormal termination of the previous session, but MiniDump does not indicate that there is data to send.

As stated several times, the worst aspect of this situation is that the message is sent anyway, regardless of attempts to cancel it.  This can lead to an embarrassing  situation because the recipient can receive a message containing errors or plain wrong information.

Upon further reflection on this problem, it is obvious that it goes away when the "Don't send" button is always available.  There is then no need to attempt brute force procedures to cancel message transmission.  These don't seem to work anyway, unless one takes the Task Manager route to terminate Pegasus.

It's up to you whether you deem it worthwhile to pursue this problem.