Wrap {Browsing,Window}Context objects sent over IPC with MaybeDiscarded
Categories
(Core :: DOM: Content Processes, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
(Blocks 1 open bug)
Details
Crash Data
Attachments
(9 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
There have been various issues, such as bug 1612894, over time due to crashes caused by code not checking for IsDiscarded
before sending a BrowsingContext over IPC. This bug adds a new MaybeDiscarded
wrapper type which allows sending a discarded BrowsingContext over IPC to another process. Helper IsNullOrDiscarded
, IsNull
, and IsDiscarded
methods make validating that the BrowsingContext
is valid easier and more explicit.
In addition, serializers for BrowsingContext*
and WindowContext*
are removed, allowing this issue to be avoided in the future.
Assignee | ||
Comment 1•5 years ago
|
||
Adds a new MaybeDiscarded wrapper type which allows sending a maybe-discarded
BrowsingContext over IPC to another process which must be explicitly checked for
nullness and discarded status before being used.
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
These serializers have been superceded by the new
MaybeDiscarded<BrowsingContext> and MaybeDiscarded<WindowContext> serializers
added in earlier parts.
Assignee | ||
Comment 8•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 9•5 years ago
|
||
Updated•5 years ago
|
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1bf5b4421e52
https://hg.mozilla.org/mozilla-central/rev/061325bfa2b7
https://hg.mozilla.org/mozilla-central/rev/aca2e3d525ca
https://hg.mozilla.org/mozilla-central/rev/08f1d33f2661
https://hg.mozilla.org/mozilla-central/rev/47a116922e81
https://hg.mozilla.org/mozilla-central/rev/be2f00ff66e6
https://hg.mozilla.org/mozilla-central/rev/69ece5421024
https://hg.mozilla.org/mozilla-central/rev/4ee2aa96e99a
https://hg.mozilla.org/mozilla-central/rev/3c87f77c919c
Comment 13•5 years ago
|
||
Hi, could you please take a look at this gv-junit multiple failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending%2Crunning%2Csuccess%2Csuperseded%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&fromchange=6da7cf8a6742e5c82833cdd2fbc58ae5010703df&searchStr=android%2C7.0%2Cx86-64%2Copt%2Ctest-android-em-7.0-x86_64%2Fopt-geckoview-junit-e10s%2C%28gv-junit%29&selectedJob=289899724
Since this bug was landed, this failure become very frequent.
Thank you.
Assignee | ||
Comment 14•5 years ago
|
||
I've been looking into this, and now have a ni? on bug 1617063. Clearing my ni? here.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•4 years ago
|
Description
•