(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.
(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.