Remove RenderTrace.
Categories
(Core :: Graphics, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox93 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: jrmuizel)
References
Details
Attachments
(1 file)
|
Assignee | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4364b684a6bd Remove RenderTrace. r=mattwoodrow
OK. This is an example of a bug I do not like. Seems to me is an issue with the review process and not with the bug filer.
I also apologize for pointing this out on this bug. I see too many bugs of this type.
Subject just says Remove RenderTrace. No explanation as to why or where it was used to support why it is no longer required.
Can we get better rationale for bugs filed by Mozilla folks as to why the change is required? Haveing a subject that says what is being doen and then doing it does not really make it for me!
|
||
Comment 4•3 years ago
|
||
Backed out for for causing bustages in nsWindow.cpp. CLOSED TREE
Link backout : https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception&revision=c51f897e354b6e59ef57fd9b428ba9ae236aa94d
Push with failures : https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception&revision=4364b684a6bdf3ad8c78876ee8e0ac901e2bc088&selectedTaskRun=W82234sbQYeFtf8247XHxg.0
Link to failure log : https://treeherder.mozilla.org/logviewer?job_id=349647013&repo=autoland&lineNumber=30530
|
|
||
Comment 5•3 years ago
|
||
(In reply to mac198442 from comment #3)
OK. This is an example of a bug I do not like. Seems to me is an issue with the review process and not with the bug filer.
I also apologize for pointing this out on this bug. I see too many bugs of this type.
Subject just says Remove RenderTrace. No explanation as to why or where it was used to support why it is no longer required.
Can we get better rationale for bugs filed by Mozilla folks as to why the change is required? Haveing a subject that says what is being doen and then doing it does not really make it for me!
WebRender, which is written in the memory-safe Rust programming language, has replaced all previous rendering codepaths (Basic, OpenGL, D3D11, Advanced Layers), which are written in the legacy C++ programming language. They are now being removed (bug 1724935). This is good for security and maintenance.
https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/
https://mozillagfx.wordpress.com/
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/38a24e21d886 Remove RenderTrace. r=mattwoodrow
(In reply to Darkspirit from comment #5)
(In reply to mac198442 from comment #3)
OK. This is an example of a bug I do not like. Seems to me is an issue with the review process and not with the bug filer.
I also apologize for pointing this out on this bug. I see too many bugs of this type.
Subject just says Remove RenderTrace. No explanation as to why or where it was used to support why it is no longer required.
Can we get better rationale for bugs filed by Mozilla folks as to why the change is required? Haveing a subject that says what is being doen and then doing it does not really make it for me!
WebRender, which is written in the memory-safe Rust programming language, has replaced all previous rendering codepaths (Basic, OpenGL, D3D11, Advanced Layers), which are written in the legacy C++ programming language. They are now being removed (bug 1724935). This is good for security and maintenance.
https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/
https://mozillagfx.wordpress.com/
Well so my point was that shuld have been stated in comment zero. so that a rationale for making the change exists. Mozilla personnel might be able to follow along on back-channels but I thought bugzilla was supposed to be a way for all Mozilla employees and volunteers to follow along and to help. hiding some information on a back channel would seem to be counter to that goal.
|
|
Assignee | |
Comment 8•3 years ago
|
||
FWIW, I try to write bug summaries proportional that future readers will get from them. In this case, the change was just removing a now unused pair of files, so it's unlikely that anyone will ever look at this bug in future.
Out of curiosity, how did you come across this bug?
|
||
Comment 10•3 years ago
|
||
| bugherder | ||
Description
•