зеркало из https://github.com/mozilla/gecko-dev.git
e12736fa36
With fission enabled, when we are starting a load, we might be saving principals for a specific browsing context in process A, and then end up targetting process B for the load, so during deserialization of the LoadInfoArgs struct, we will end up using principals that were saved during a previous load targetting that browsing context (with the same id) but in process B. Therefore, we cannot assert (without clearing the saved principals in the original browsing context when a load is done, which can be done as a follow up work) that the saved principal will be equal to the serialized one from LoadInfoArgs. Differential Revision: https://phabricator.services.mozilla.com/D89728 |
||
---|---|---|
.. | ||
app | ||
chromium | ||
contentproc | ||
glue | ||
gtest | ||
ipdl | ||
mscom | ||
testshell | ||
moz.build | ||
pull-chromium.py |