Whole browser window turn white and completely broken
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox98 | --- | unaffected |
| firefox99 | --- | unaffected |
| firefox100 | --- | verified |
People
(Reporter: alice0775, Unassigned)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Crash Data
Attachments
(1 file)
|
28.97 KB,
text/plain
|
Details |
[Tracking Requested - why for this release]: Nightly build is unusable
Steps to reproduce:
- Start with new profile
--- observe, back/forward button - Right click on toolbar and select Customize Toolbar...
--- observe, Whole browser window turn white and completely broken
OR
- Start with -p
- Click
Create Profilebutton
--- observe, Whole browser window turn white and completely broken
Actual Results:
Whole browser window turn white and completely broken
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8021329633d61aa2044dabdf715df445fed7ae82&tochange=89ae192e54343b26b2f1617fcc985213fa98f1f4
Nicolas Silva, Your patch seems to cause the regression. Could you please look into this? Or please backed it out asap.
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 1•3 years ago
|
||
Screencast 1 : https://youtu.be/8xelW1iZpSI
Screencast 2 : https://youtu.be/4cnudum6IzA
|
|
Reporter | |
Comment 2•3 years ago
|
||
|
||
Comment 3•3 years ago
|
||
The patch is being backed out in another bug
|
|
Reporter | |
Comment 4•3 years ago
|
||
(In reply to Nicolas Silva [:nical] from comment #3)
The patch is being backed out in another bug
I verified fix this in Nightly100.0a1(20220316095231) Windows10.
|
|
Reporter | |
Updated•3 years ago
|
|
|
||
Updated•3 years ago
|
|
|
||
Comment 5•3 years ago
|
||
Hi, could you try this build and report whether the bug occurs on it as well? https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/H8QrsDkdRqGxYBci8Q7iPw/runs/0/artifacts/public/build/target.zip
It has a subset of the changes in bug 1757588 I'm trying to bisect which part caused the issue.
Thanks!
|
|
Reporter | |
Comment 6•3 years ago
|
||
(In reply to Nicolas Silva [:nical] from comment #5)
Hi, could you try this build and report whether the bug occurs on it as well? https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/H8QrsDkdRqGxYBci8Q7iPw/runs/0/artifacts/public/build/target.zip
It has a subset of the changes in bug 1757588 I'm trying to bisect which part caused the issue.
Thanks!
The try build is working fine. I cannot reproduce this.
|
|
||
Comment 7•3 years ago
|
||
Hi, sorry to bother you again. Could you try this build? It contains the feature that caused the regression you experienced on some AMD hardware, but written differently in the hope that it won't cause the issue: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/c-d76Z0eTYubMRxoZD8YcQ/runs/0/artifacts/public/build/target.zip
Thanks!
|
|
Reporter | |
Comment 8•3 years ago
|
||
(In reply to Nicolas Silva [:nical] from comment #7)
Hi, sorry to bother you again. Could you try this build? It contains the feature that caused the regression you experienced on some AMD hardware, but written differently in the hope that it won't cause the issue: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/c-d76Z0eTYubMRxoZD8YcQ/runs/0/artifacts/public/build/target.zip
Thanks!
The try build is also working fine. I cannot reproduce this.
Description
•