Created attachment 8750107 Bug 336193 handle SIGTERM in SignalPipeWatcher then in the main thread to quit
What about the attempt in this patch? I intercept SIGTERM using "SignalPipeWatcher" as suggested, then I pass a task to the main thread so it calls "nsIAppStartup::Quit(nsIAppStartup::eForceQuit)". That may seem convoluted, it would look better if it was done in one go. I don't have any experience on the Firefox codebase, so I may completely misunderstand the issues. If "Quit" is executed by the main thread (like it would be after a keyboard key for example), wouldn't it avoid the aforementioned problems with the locks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/73536 Title: MASTER Firefox crashes on instant X server shutdown Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Triaged Bug description: Firefox crashes when X server is forcefully torn down (e.g. by pressing ctrl-alt-backspace) and a crash report gets generated on next login. (Original Report: I've reproduced it once on my machine with the following steps. With, oh, about 5 tabs open, I just pressed ctrl-alt-backspace, logged back in when the X server restarted, and FF crashed with a bug report when Gnome tried to restore the session. It's not terribly important, I don't think anyone does this very often, but maybe it'll be helpful. ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
