Closed Bug 1277067 Opened 5 years ago Closed 5 years ago
IAsync Shutdown .content Child Shutdown
Once the users of this are removed, then we should remove it so nobody starts using it. We want to avoid it because it slows down the shutdown of content processes in release builds.
We shouldn't forget to document in the idl and jsm why we're doing this. Otherwise, people will just re-add it.
(In reply to David Rajchenbach-Teller [:Yoric] (please use "needinfo") from comment #1) > We shouldn't forget to document in the idl and jsm why we're doing this. > Otherwise, people will just re-add it. That sounds reasonable. It shouldn't be a long-term risk, because there is work underway to make the other user of content-child-shutdown, telemetry, not use it, whereupon it can be removed entirely.
try run (with patches for the other blocking bugs): https://treeherder.mozilla.org/#/jobs?repo=try&revision=dbb7fd16bff0
Attachment #8758738 - Flags: review?(dteller)
Attachment #8758738 - Flags: review?(dteller) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/efcca7d36ad4 Remove nsIAsyncShutdown.contentChildShutdown. r=Yoric
You need to log in before you can comment on or make changes to this bug.