New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 503608 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2015
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

gl_PointSize not working on Intel HD5500

Reported by ulysses....@gmail.com, Jun 23 2015

Issue description

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

Steps to reproduce the problem:
Go to https://www.khronos.org/registry/webgl/sdk/tests/conformance/rendering/point-size.html?webglVersion=1. Tests fail.

I first ran into this when working on a project that requires gl_PointSize. It seems to be working in Firefox and on Windows versions of Chrome.

What is the expected behavior?
All tests pass and gl_PointSize is usable elsewhere.

What went wrong?
WebGL conformance tests are failing.

Did this work before? N/A 

Chrome version: 43.0.2357.125  Channel: n/a
OS Version: 43.0.2357.125
Flash Version: Shockwave Flash 18.0 r0
 
Cc: ssamanoori@chromium.org
Labels: Needs-Feedback
Unable to repro the issue on Nvidia graphs card on Ubuntu 14.04 using latest stable 43.0.2357.130, canary 45.0.2441.3 with below steps:

1.Opened url:https://www.khronos.org/registry/webgl/sdk/tests/conformance/rendering/point-size.html?webglVersion=1.
2.All tests pass.

Please find attached screenshot.
Request you to check the issue on latest chrome version and update us if issue still persists.
503608.png
203 KB View Download
I too see this problem.
I have an Intel N2840 (Bay Trail) running Ubuntu 15.04.
Chrome version is: 43.0.2357.130 (64-bit).

Firefox on the same system does not exhibit this problem.

Points seem to always have a size of 1 even when gl_PointSize is set in the vertex shader.
ScreenshotOfChromeWebglTest.png
177 KB View Download
I do not see this problem with Chromium (compiled from source yesterday) or with Chrome Beta (Version 44.0.2403.61 beta (64-bit)).
Both tests where run on my Intel N2840 (Using it's Bay Trail GPU) which, as mentioned in my last post, exhibits this bug when using Chrome 43.0.2357.130 (64-bit).

Hopefully this means that this bug has been fixed and the fix will appear in the release version of Chrome soon.
I too have this issue with Intel graphics in Chrome on Ubuntu 14.04.  The problem goes away with the nvidia driver or using Firefox.  Here's some output from http://webglreport.com/ in the failing Chrome 43.0.2357.130...

Platform:	Linux x86_64
Browser User Agent:	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Context Name:	webgl
GL Version:	WebGL 1.0 (OpenGL ES 2.0 Chromium)
Shading Language Version:	WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
Vendor:	WebKit
Renderer:	WebKit WebGL
Unmasked Vendor:	Intel Open Source Technology Center
Unmasked Renderer:	Mesa DRI Intel(R) Ivybridge Mobile
Antialiasing:	Available
ANGLE:	No
Major Performance Caveat:	No
Oops, missed that last post.  This test now passes for me in Version 44.0.2403.61 beta (64-bit).
This now seems to be fixed in the latest release version (Version 44.0.2403.89 (64-bit)).
Cc: tkonch...@chromium.org
This test is passing now on latest stable 44.0.2403.125 and canary

ulysses.popple@, Could you please recheck on latest stable and confirn us so that we can close this issue.
Ah, didn't realize you needed confirmation from me. Confirmed passing on 44.0.2403.125.
Status: WontFix
As per confirmation from comment #8 we are closing this issue. Please feel free to file a new issue if you encounter any issue with chrome in future.

Sign in to add a comment