101715 - mozilla doesn't handle SIGXCPU graacefully

Status: NEW

(SeaMonkey :: UI Design, defect)

Description

[Brian Ristuccia]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091311

When mozilla receives SIGXCPU, it should clean up and then exit. For example,
the mail client should save messages currently being composed in the drafts folder. 

Reproducible: Always
Steps to Reproduce:
1. ulimit -S -t 30 ; ulimit -H -t 60
2. compose a message, but don't send yet. 
3. use mozilla for a while
4. mozilla catches SIGXCPU, and exits without cleaning up or saving. Your
message is lost. 

Actual Results:  Mozilla quit abruptly when it reached the soft CPU time limit.

Expected Results:  Mozilla should have cleaned up as quickly as possible to
avoid data loss and hitting the hard CPU limit.

Comment 1

[Boris Zbarsky [:bzbarsky]]

ccing blizzard because he may know something about this...

Comment 2

[Christopher Blizzard (:blizzard)]

Interesting.  I don't know how to fix that.  It's an interesting issue, though.

Comment 3

[Sheela Ravindran]

confirming 

Comment 4

[Jean-Francois Ducarroz]

not really my domain! Seems more a XPApp generic problem than just a msg compose
one to me. Reassign...

Comment 5

[Peter Trudelle]

->bryner

Comment 6

[Brian Ryner (not reading)]

-> future.  I don't think this is something the vast majority of users will
encounter.

Comment 7

[brianr-bugzilla.mozilla.org]

It might make sense to lump this bug into a more generic "clean up before crashing" bug if one exists. For example, there are other signals which indicate impending disaster but would still allow Mozilla to at least attempt some basic cleanup before exiting. 

Comment 8

[Tony Mechelynck [:tonymec]]

How does SeaMonkey (how do the Mozilla apps) handle SIGTERM? Shouldn't the cases be similar?