(In reply to Nathan Froyd (:froydnj) from comment #31) > I assume you mean re-raising once we've handled application shutdown?
Yes. > Oof, that's quite some complexity. Yes, it could well be too much trouble. It can be attacked separately if/when that turns out to be important for anything. > And for things like nsProfileLock, it seems like > a proper invocation of the shutdown process, as triggered by this patch, > makes much more sense than trying to invoke nsProfileLock's signal handlers. Yes, a proper shutdown is definitely the appropriate response to the first signal. If the lock has been removed, then subsequently running nsProfileLock's handlers should be harmless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/73536 Title: MASTER Firefox crashes on instant X server shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
