mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-13 05:15:45 +00:00
13e936cdab
The intermittent failure appears to have been due to mOriginsHavingData only being updated when the db thread flushes. The db thread has a hard-coded 5 second flush interval. It's likely that e10s startup was previously so slow that we were assured of having a flush happen by the time our fresh process created its parent actor. We correct this by reliably ensuring a flush before spinning up the process to check preload state. We also ensure a flush at the start of the test for our check that there was no preload in the initial cases. We were actually more vulnerable in that case, I believe, but as a browser chrome test, there were no other tests that would have used content localStorage. We additionally ensure that the content process has received and populated mOriginsHavingData by having the tab opening process wait for about:blank to load in the process before actually opening our origin. Prior to this change we were depending on orderings that aren't guaranteed. --HG-- extra : rebase_source : 92d3c675cee82ffe8b562e83860601e0c6dc1a9b |
||
|---|---|---|
| .. | ||
| browser | ||
| html | ||
| js | ||
| mochitest | ||
| reftest | ||
| unit | ||
| moz.build | ||