Don't recreate session-store's history listener for browsing-context-did-set-embedder notification if browserId didn't change
Categories
(Firefox :: Session Restore, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: peterv, Assigned: peterv)
References
(Regressed 1 open bug)
Details
Attachments
(1 file)
This is causing issues when enabling SHIP on Android, because we end up resetting the listener and notifying multiple times about history changes. Both desktop and Android have the same code to install this listener, so we should fix both.
Assignee | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
The severity field is not set for this bug.
:sfoster, could you have a look please?
For more information, please visit BugBot documentation.
Comment 3•1 year ago
|
||
:peterv, can you provide a severity estimate? Sounds like maybe s3?
Assignee | ||
Updated•1 year ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Comment 5•11 months ago
|
||
bugherder |
Comment 6•10 months ago
|
||
(In reply to Pulsebot from comment #4)
Pushed by pvanderbeken@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2fd6571608c5
Don't recreate session-store's history listener for
browsing-context-did-set-embedder notification if browserId didn't change.
r=geckoview-reviewers,nika,sessionstore-reviewers,owlish,kaya,farre
Perfherder has detected a talos performance change from push 2fd6571608c562d4703ad38ef440cb9c437d0046.
Improvements:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
3% | cross_origin_pageload | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 257.46 -> 250.26 |
3% | cross_origin_pageload | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 257.58 -> 250.41 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run these tests on try with ./mach try perf --alert 161
For more information on performance sheriffing please see our FAQ.
Description
•