Comment 20 for bug 73536

(In reply to comment #7)
> (In reply to comment #4)
> > > Should SIGTERM cause eAttemptQuit (prompting the user if there is unsaved
> > > work/multiple tabs), or eForceQuit?
> >
> > That's a harder question and I think there is no rule for that. I tend to vote
> > for eForceQuit since if the application gets a SIGTERM the user may not be in
> > front of the application (or display) at all.
>
> I also think eForceQuit is better, although it would be fine to have at least
> some SIGTERM handling at all. I often just start ./firefox from the commandline
> when developing my extension and ctrl-c it when done with the result of getting
> a "do you want to restore tabs" message at next start :(
>

There is sent SIGINT on Ctrl+C instead of SIGTERM.