(In reply to Ted Mielczarek [:ted] from comment #19) > Breakpad doesn't handle SIGTERM, so you should be okay there. You will > probably need to make sure that your code interacts properly with the > profile locking code, since the purpose of that signal handler is to clean > up the profile lock correctly upon exit.
Doing a clean exit (nsAppShell::Exit) from handling the signal won't cause the profile unlocking code to be run? I do still see a .parentlock in my profile. This is going to be tricky: we can't run the old signal handler before nsAppShell::Exit, because nsProfileLock's signal handlers run _exit or the SIG_DFL handler, which would exit. But we can't run the old signal handler after nsAppShell::Exit because we've exited. -- 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
