Currently there are issues with BrowsingContext objects when fission is enabled. For example, when a process switch occurs, there can be races between the content process sending a request to the parent and the parent process changing the current "owner" for a browsing context. This can lead to crashes such as bug 1561155. We should clean up the process switching logic, and prevent races like this while there are ongoing process switches. This will likely require changes around the code in (WindowGlobalParent::ChangeFrameRemoteness)[https://searchfox.org/mozilla-central/rev/07f7390618692fa4f2a674a96b9b677df3a13450/dom/ipc/WindowGlobalParent.cpp#280-343].
Bug 1566538 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently there are issues with BrowsingContext objects when fission is enabled. For example, when a process switch occurs, there can be races between the content process sending a request to the parent and the parent process changing the current "owner" for a browsing context. This can lead to crashes such as bug 1561155. We should clean up the process switching logic, and prevent races like this while there are ongoing process switches. This will likely require changes around the code in [WindowGlobalParent::ChangeFrameRemoteness](https://searchfox.org/mozilla-central/rev/07f7390618692fa4f2a674a96b9b677df3a13450/dom/ipc/WindowGlobalParent.cpp#280-343).