Weird glitches issues in latest beta version with WebRender enabled
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: mcbeckler, Assigned: kvark)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
(deleted),
video/quicktime
|
Details | |
(deleted),
text/plain
|
Details | |
(deleted),
application/zip
|
Details | |
(deleted),
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
Received latest update, immediately starting having a strange rendering issues when loading pages.
Running macOS 10.13.6 on a 2011 MBP.
Actual results:
It looks like the painting of elements is incomplete when the page is loading. Most block elements seem to all have a similar distorted image, and most text is completely garbled. It's also unusual in that can affect the entire browser, not just the page, but also the URL bar and associated buttons/icons. It was inconsistent to reproduce, but it seems to happen if I visit a opened tab that I had not visited recently. Screen recording of bug is attached.
Expected results:
Normal rendering of webpage.
To clarify, observing the bug in the URL bar was inconsistent to reproduce. I could reproduce this bug consistently by visiting a site that took time to load, such as Reddit.
Seems like it's related to dynamically generated elements rendered after loading.
I've not observed it on any sites that are server-side rendered, only client-side.
Comment 3•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 4•4 years ago
|
||
Can you attach your about:support information? Does the bug go away if you change gfx.webrender.force-disabled
to true
in about:config
(and restart?)
Hey Emilio, it does seem to resolve when I set gfx.webrender.force-disabled
to true
and restart my browser.
I attached my about:support
in the comment above, and that grab was from before I set that configuration item.
Let me know if you need anything else!
Comment 7•4 years ago
|
||
No, that was super helpful, thanks!
Dzmitry, does this ring any bell?
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
I don't know what this is. It would be most awesome to get a continuous WR capture out of this.
In Nightly, it would be started by hitting "ctrl+shift+6" and stopped by the same combo. The wr-capture
folder would appear in the home folder, which needs to be zipped and uploaded somewhere.
@mcbeckler, would you be able to get it?
Hey @kvark,
I downloaded nightly, and the effect was much more exaggerated than in the beta channel.
I was able to get the captures, but I don't know which one you'll want, so I'm uploading both.
Reporter | ||
Comment 10•4 years ago
|
||
Reporter | ||
Comment 11•4 years ago
|
||
The second capture was far too large for Bugzilla, so you should be able to download it here: download link
Let me know if you have any issues downloading it.
Assignee | ||
Comment 12•4 years ago
|
||
Amazing, thank you!
I'll try to look at them tomorrow
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
|
||
The captures don't show anything strange, they look normal. I wasn't able to replay the "frame" level, since it requires direct composition, which we don't have yet in Wrench, but the "scene" replay is alright. There is a tiny chance that something bad happened to frame building, surely. However, I'm more suspicious of HD3000 GPU in the affected machine. It's very old, and given the state of macOS GL drivers in general, and early Intel drivers in particular, I'd more likely believe this to be a driver/HW issue. This is also supported by the fact we are seeing this as a single occurrence in beta, and this somehow wasn't caught in Nightly.
I suggest us to block WR on HD3000 family on Intel, at least until we have our hands on one of these, and reproduce this.
Assignee | ||
Comment 14•4 years ago
|
||
Updated•4 years ago
|
Reporter | ||
Comment 15•4 years ago
|
||
I think that's a reasonable solution, and I suspect you're probably right.
Thank you for looking into this!
Updated•4 years ago
|
Updated•4 years ago
|
Comment 16•4 years ago
|
||
There are a few Beta 81 MacOS crashes with a HD3000: https://crash-stats.mozilla.org/search/?adapter_device_id=0x0126&product=Firefox&version=81.0b1&version=81.0b2&version=81.0b3&platform=Mac%20OS%20X&process_type=browser&date=%3E%3D2020-08-22T02%3A47%3A00.000Z&date=%3C2020-08-29T02%3A47%3A00.000Z&_facets=signature&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports
Some mention "AppleIntelHD3000GraphicsGLDriver".
Comment 17•4 years ago
|
||
Comment 18•4 years ago
|
||
bugherder |
Assignee | ||
Comment 19•4 years ago
|
||
Comment on attachment 9172793 [details]
Blocklist WR on mac Intel HD3000
Beta/Release Uplift Approval Request
- User impact if declined: macOS users with Intel HD3000 experience glitches and crashes
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): It's just a blocklist update, should be harmless
- String changes made/needed:
Comment 20•4 years ago
|
||
Comment on attachment 9172793 [details]
Blocklist WR on mac Intel HD3000
Approved for 81.0b5.
Comment 21•4 years ago
|
||
bugherder uplift |
Description
•