Open
Bug 1688678
(wr-linux-amd-driver)
Opened 5 years ago
Updated 1 year ago
[meta] WebRender AMD proprietary driver metabug
Categories
(Core :: Graphics: WebRender, task, P5)
Tracking
()
NEW
People
(Reporter: aosmond, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Most users just use the Mesa drivers, but some use the proprietary drivers from AMD. This metabug tracks them, although it is unlikely we will fix them given how few users there are relatively.
| Reporter | ||
Updated•5 years ago
|
Alias: wr-linux-amd-driver
Comment 1•5 years ago
|
||
Bug 1438215 is related but not necessarily a blocker for WebRender: if we're using fglrx in a child process, the sandbox will have to be significantly weaker (allowing direct filesystem access, if the guesses about fglrx's behavior in that bug are correct) than what we can do with Mesa or nvidia. That was a problem if it would have been used for WebGL in a content process, but would be more tolerable in a dedicated compositor process that's not running hostile JS, and it doesn't matter if it's used in the unsandboxed parent process.
Depends on: 1438215
You need to log in
before you can comment on or make changes to this bug.
Description
•