Google Docs is twitchy and rendering incorrectly on Ubnutu 24 w/ NVIDIA 550
Categories
(Core :: Graphics: Canvas2D, defect, P2)
Tracking
()
People
(Reporter: bhood, Assigned: lsalzman)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
54.69 KB,
text/plain
|
Details | |
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
|
Details | Review |
Ubuntu 24.04.01 LTS using NVIDIA 550 driver on an RTX 2080 Ti GPU.
Google Docs is rendering pages incorrectly. From the attached video, you can see that it flashes back and forth between two unrelated documents, leaving them intertwined once it has settled down. Specifically in the video, it is leaking data from a "confidential" document that was opened in the browser some hours earlier but is now no longer open.
I recently upgraded my system from Ubuntu 22.04 LTS, which updated the NVIDIA driver from 535 to 550.
I tested this behavior in Chrome on the same system, and it does not display this issue. Indeed, much to my distaste, I must use Chrome in order to properly edit documents at the moment.
The only STR I can provide is to open a Google Doc in a similarly configured machine.
Reporter | ||
Updated•1 month ago
|
Reporter | ||
Comment 1•1 month ago
|
||
Assignee | ||
Comment 2•1 month ago
|
||
Sotaro and Martin, this seems like it may be a DMABuf/Nvidia-ish compositing issue? Ideas?
Reporter | ||
Comment 3•1 month ago
|
||
I've disabled gfx.canvas.accelerated
(as suggested in 1917225) and that seems to be working around the issue so far.
Comment 4•1 month ago
|
||
I see many similar reports from Fedora users which run NVIDIA drivers, for instance Bug 1908370. Yes, looks like related to dmabuf but I have no idea how. As it's NVIDIA only I'd report it to NVIDIA as their driver bug. Looks like it affects both X11 and Wayland.
Comment 5•1 month ago
|
||
Disable dmabuf on the affected drivers may be an option.
Reporter | ||
Comment 7•1 month ago
|
||
I think I've confirmed with Lee that setting widget.dmabuf.enabled
to false while leaving gfx.canvas.accelerated
enabled addresses the glitching.
Comment 8•1 month ago
|
||
I wonder if Bug 1907828 might be related to this bug.
Updated•24 days ago
|
Reporter | ||
Comment 9•18 days ago
|
||
According to comment 35 in bug 1907828 (the See Also
cited above), setting widget.dmabuf.enabled
to false
does not fix that other issue. I'm not sure these two are connected, since it does in this reported use case.
Assignee | ||
Comment 10•17 days ago
|
||
This adds a DMABUF_WEBGL feature that can be independently blocklisted from DMABUF itself.
After that, this adds a blocklist entry for the Nvidia driver which gives incorrect rendering.
Updated•17 days ago
|
Comment 11•16 days ago
|
||
Reporter | ||
Updated•16 days ago
|
Comment 12•16 days ago
|
||
Assignee | ||
Updated•16 days ago
|
Comment 14•15 days ago
|
||
Comment 15•15 days ago
|
||
bugherder |
Assignee | ||
Comment 22•13 days ago
|
||
Comment on attachment 9434689 [details]
Bug 1924578 - Disable DMABUF_WEBGL on Nvidia driver. r?aosmond
Beta/Release Uplift Approval Request
- User impact if declined/Reason for urgency: Incorrect rendering for Linux + Nvidia users.
- Is this code covered by automated tests?: Unknown
- Has the fix been verified in Nightly?: Yes
- 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): This adds a blocklist entry to disable a buggy feature affected users.
- String changes made/needed:
- Is Android affected?: No
Comment 23•12 days ago
|
||
Comment on attachment 9434689 [details]
Bug 1924578 - Disable DMABUF_WEBGL on Nvidia driver. r?aosmond
Approved for 133.0b5
Comment 24•12 days ago
|
||
uplift |
Updated•12 days ago
|
Comment 27•3 days ago
|
||
We've blocked DMABUF for NVIDIA binary driver users in Firefox 132 and earlier. DMABUF will come back for Firefox 133+, released on Nov 26, but DMABUF + WebGL will still be blocked by the hard coded rule in Firefox itself.
Description
•