103270 - No save of new message composition on SIGTERM

Status: NEW

(MailNews Core :: Composition, defect)

Description

[Rob W.W. Hooft]

When a SIGTERM signal arrives (e.g. a pending shutdown, or an accidental 
"kill %") all messages that are being composed at that moment are lost.

They could/should be saved somewhere for later continuation.

Comment 1

[Sheela Ravindran]

Reporter,
Give more information of build id. Also can you give some steps to be able to 
see this problem.

Comment 2

[Sheela Ravindran]

Confirming(2001-12-03-06 linux rh 6.2, gnome 4.5.42). Changing this to an 
enhancement. When you have the application open and composing a message. Try to 
kill the application. I see the warning dlg saying that all the changes would be 
lost. And the mail that was still being composed is not saved.

This is not very critical because there is a warning dlg that comes up not from 
the application though which kind of should give a clue that the mail composed 
will be lost. This dlg has cancel and OK.  So you can cancel and save that 
message in case of an accidental kill.  

Comment 3

[Mikko Rantalainen]

IMO when SIGTERM is received message should be immediatly saved at least to
local harddrive if possible, because in worst case it could be that system is
shutting down and after 10 seconds we'll get SIGKILL if we aren't done - waiting
for user decision might cause a problem.

Also as a related issue if SIGSEGV is received at least something should be
tried to save from currently unsaved messages to prevent data loss.