Make ContentParent::ShutDownProcess fallible in case of failed dispatch
Categories
(Core :: DOM: Content Processes, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox109 | --- | fixed |
People
(Reporter: jstutte, Assigned: aiunusov)
References
Details
Attachments
(2 files)
ContentParent::ShutDownProcess
currently does not give any return value if the dispatching of the shutdown messages was successful or not. This makes it impossible to avoid potential races 100% (even if we check CanSend()
before calling it that might change in the time frame we need to arrive at the real dispatch) and might leave us to believe we need to wait for a process shutdown that will never happen.
We should make it return a boolean if the dispatch was successful or not, just like a normal dispatch function.
Reporter | ||
Updated•11 months ago
|
Assignee | ||
Updated•4 months ago
|
Assignee | ||
Comment 1•4 months ago
|
||
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/65b98515f2ce Make ContentParent::ShutDownProcess fallible in case of failed dispatch, r=smaug
Comment 3•4 months ago
|
||
bugherder |
Assignee | ||
Comment 4•4 months ago
|
||
prevent resource leak). r=smaug
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/acbc96016140 Use KillHard() in case of failed dispatch (in order to r=smaug
Comment 6•4 months ago
|
||
bugherder |
Comment 7•4 months ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Description
•