chrome:gpu report "WebGL Hardware Accelerated", but WebGL not working
Reported by
olivier....@gmail.com,
Mar 10 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. open a webgl page (threejs samples) What is the expected behavior? Beautiful 3D What went wrong? Cannot create webgl context. Did this work before? N/A Chrome version: 48.0.2564.116 Channel: stable OS Version: 8.1 (Windows NT 6.3) Flash Version: Shockwave Flash 21.0 r0 This happen on this laptop : Dell Latitude 14 E7450 Internet Explorer 11 is displaying webgl pages correctly.
,
Mar 11 2016
olivier@ - Thanks for the issue. Could you please provide the sample test case of this issue as an attached file or URL of the webpage where we can test this issue from QA end. Before updating this bug please recheck this issue on latest chrome stable M49-49.0.2623.87 and let us know if issue still persists or not. Thanks!
,
Mar 14 2016
Submitter: it would be better if you'd copy/paste the output of about:gpu rather than creating a PDF. The formatting isn't important, but the PDF's lost valuable information off the right-hand side. Regardless, for this GL_RENDERER: GL_RENDERER ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0) the following errors are being reported in about:gpu: [7676:6272:0310/083029:ERROR:texture_manager.cc(2202)] : [.RenderWorker-011D3670.GpuRasterization]GL ERROR :GL_INVALID_OPERATION : glTexImage2D: <- error from previous GL command ... [7676:6272:0310/083029:ERROR:gles2_cmd_decoder.cc(6612)] : [.RenderWorker-011D3670.GpuRasterization]GL ERROR :GL_INVALID_OPERATION : glRenderbufferStorageMultisampleCHROMIUM: <- error from previous GL command Is there a possibility that GPU rasterization is using an extension ANGLE doesn't support on this GPU?
,
Mar 14 2016
I'm sorry the report was already truncated, and it is from a customer computer. Any webgl demo, even the simplest one, will fails at the wegl context creation.
,
Mar 14 2016
Can the customer try Canary, and if necessary Dev and Beta, to see whether the problem's already been fixed?
,
Mar 14 2016
No, they have a really strict it department. The latest version we were able to try on was 48.
,
Mar 15 2016
Thank you for providing more feedback. Assigning to requester "brajkumar@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2016
olivier@ - Any update on this bug? Is this issue still seen on latest chrome versions? Could you please recheck this issue on latest stable M50 and kindly update this bug with latest behavior. Thanks!
,
May 2 2016
Issue 597522 has been merged into this issue.
,
May 15 2016
same happens here, on dx9 hardware. http://webglreport.com/ says webgl is supported, but disabled or unavailable. gpu info: http://wklej.org/hash/8705602901b/txt/
,
Jul 14 2016
Due to lack of user response from the original reporter closing this issue, Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by olivier....@gmail.com
, Mar 10 2016139 KB
139 KB Download