New issue
Advanced search Search tips

Issue 833984 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 817400
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 817400



Sign in to add a comment

Read pixels broken in Chrome/Chromium on Ubuntu 18.04 using the NVIDIA driver

Reported by dmiller...@gmail.com, Apr 17 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Ubuntu 18.04 system with an NVIDIA 980 or 1070 card (these are the only 2 cards I have) using Chrome or Chromium with the NVIDIA proprietary drivers.
2. Open Chrome/Chromium to https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html and run the all/conformance/reading tests.
3. The 2nd and 3rd of the 3 read pixels tests will fail.

What is the expected behavior?
The read pixel conformance tests should pass.

These tests do pass on Firefox, and web pages that use read pixels (photoeditor.polarr.co) function correctly in Firefox on Ubuntu 18.04 but not in Chrome.

What went wrong?
Read pixel values are all 0,0,0 in Chrome and Chromium.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 65.0.3325.181  Channel: stable
OS Version: Ubuntu 18.04
Flash Version: 

I originally reported this bug on LaunchPad and was directed to open an issue here. Apport collected my system information and attached it to the issue on Launchpad.
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1764648

Ubuntu 18.04 is in final beta and is scheduled for release on April 26th.
 
Correction: The pixel values are mostly 0,0,0, though some are just garbled.
Screenshot from 2018-04-17 12-16-08.png
668 KB View Download
Screenshot from 2018-04-17 12-15-53.png
1.9 MB View Download
Blockedon: 817400
This sounds like  issue 817400 , which was worked around in Chrome 66. Chrome 66 should be coming ~this week. Could you confirm whether the issue is fixed in Chrome 66? (you can get it now by installing the Beta channel)
I just installed Chrome 66 beta and 67 dev, and the issue is fixed in both of those.

Comment 4 by zmo@chromium.org, Apr 17 2018

Mergedinto: 817400
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment