The FPS overlay (layers.acceleration.draw-fps) doesn't work when CoreAnimation is enabled
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | wontfix |
firefox71 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
References
(Regression)
Details
(Keywords: regression)
Attachments
(7 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 |
In bug 1574745 I broke the FPS overlay in configurations that use native layers, i.e. macOS with CoreAnimation. So the layers.acceleration.draw-fps pref doesn't do anything there at the moment.
The work in this bug will bring the FPS overlay back.
(This is not that urgent and does not need to be tracked for Firefox 70, it's a pref that is only occasionally used by Gecko developers.)
Assignee | ||
Comment 1•5 years ago
|
||
Depends on D44330
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D44332
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D44333
Assignee | ||
Comment 4•5 years ago
|
||
Depends on D44334
Assignee | ||
Comment 5•5 years ago
|
||
Depends on D44335
Assignee | ||
Comment 6•5 years ago
|
||
This creates and updates layers that draw the same things as RenderDebugOverlay().
The code is duplicated so that the overlay can be independent of the compositing
layer content drawing. All layers need to be drawn first, and the GPU stats from
that layer are shown in mGPUStatsLayer.
Depends on D44336
Assignee | ||
Comment 7•5 years ago
|
||
This makes the fill rate numbers which are displayed in the FPS overlay a lot more reasonable.
It also requires the TransformAndClipBounds fix from bug 1578045 for correct numbers.
Depends on D44337
Comment 9•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6f8f8f958da7
https://hg.mozilla.org/mozilla-central/rev/e408b810106d
https://hg.mozilla.org/mozilla-central/rev/1d43d31f95ed
https://hg.mozilla.org/mozilla-central/rev/9b78526a3b4a
https://hg.mozilla.org/mozilla-central/rev/d8a238d4c34d
https://hg.mozilla.org/mozilla-central/rev/f8ced2588497
https://hg.mozilla.org/mozilla-central/rev/12a11f3c8ab4
Updated•5 years ago
|
Comment 10•5 years ago
|
||
Is this going to ride Fx71 to release?
Assignee | ||
Comment 11•5 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #10)
Is this going to ride Fx71 to release?
I think that would be acceptable. The alternative would be to uplift both bug 1578099 and this bug to 70, including the three regression fixes from bug 1578310, bug 1578376 and bug 1578305. I'd rather wait for any remaining regressions to shake out before doing that.
Updated•5 years ago
|
Updated•3 years ago
|
Description
•