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

Issue 657908 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

seems to be issue with webgl accessing a chrome extension

Reported by gaurav.g...@globallogic.com, Oct 20 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
1. add extension (https://chrome.google.com/webstore/detail/pnacl-examples/mblemkccghnfkjignlmgngmopopifacf)
2. launch app 
3. click graphics 3d
4. on some similar os machines I can see graphics 3d rotating cube and on some its failing and can't see any rotating cube and details are same for every machine where its failing, refer what went wrong for further details.

What is the expected behavior?
1. add extension (https://chrome.google.com/webstore/detail/pnacl-examples/mblemkccghnfkjignlmgngmopopifacf)
2. launch app 
3. click graphics 3d
4. Graphics 3d cube rotate

What went wrong?
Installed PNACI Examples app on chrome version 51 (chrome-extension://mblemkccghnfkjignlmgngmopopifacf/index.html)

Its working on few machines and failing on few with same error message and same gpu details as below.

It’s not running graphics 3d example. To debug analysed graphics:gpu following are the details.
Graphics Feature Status
•	Canvas: Software only, hardware acceleration unavailable
•	Flash: Software only, hardware acceleration unavailable
•	Flash Stage3D: Software only, hardware acceleration unavailable
•	Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
•	Compositing: Software only, hardware acceleration unavailable
•	Multiple Raster Threads: Unavailable
•	Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
•	Rasterization: Software only, hardware acceleration unavailable
•	Video Decode: Software only, hardware acceleration unavailable
•	Video Encode: Software only, hardware acceleration unavailable
•	WebGL: Unavailable
Driver Bug Workarounds
•	clear_uniforms_before_first_program_use
•	disable_direct_composition
•	disable_discard_framebuffer
•	exit_on_context_lost
•	scalarize_vec_and_mat_constructor_args
Problems Detected
•	GPU process was unable to boot: GPU process launch failed.
Disabled Features: all
•	Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
•	Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
•	Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
•	Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
•	Direct composition flashes black initially on Win <10: 588588
Applied Workarounds: disable_direct_composition
•	Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported	20/10/2016, 22:54:06
Chrome version	Chrome/51.0.2704.103
Operating system	Windows NT 6.1 SP1
Software rendering list version	0
Driver bug list version	8.66
ANGLE commit id	1a1b30c37e13
2D graphics backend	Skia
Command Line Args	Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-devtools-experiments --enable-gpu-rasterization --enable-webgl-draft-extensions --ignore-gpu-blacklist --enable-features=WebRTC-H264WithOpenH264FFmpeg --flag-switches-end
Driver Information
Initialization time	0
In-process GPU	true
Sandboxed	false
GPU0	VENDOR = 0x0000, DEVICE= 0x0000
Optimus	false
AMD switchable	false
Desktop compositing	none
Driver vendor	
Driver version	
Driver date	
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	
GL_RENDERER	
GL_VERSION	
GL_EXTENSIONS	
Disabled Extensions	
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Direct rendering	Yes
Reset notification strategy	0x0000
GPU process crash count	0
Compositor Information
Tile Update Mode	One-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	Software only
BGRX_8888	Software only
BGRA_8888	Software only
YUV_420	Software only
YUV_420_BIPLANAR	Software only
UYVY_422	Software only
Diagnostics
... loading ...
Log Messages
•	[2156:12504:1020/225025:ERROR:angle_platform_impl.cc(33)] : ANGLE Display::initialize error 4: Could not create D3D11 device.
•	[2156:12504:1020/225025:ERROR:gl_surface_egl.cc(594)] : eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type
•	[2156:12504:1020/225026:ERROR:angle_platform_impl.cc(33)] : ANGLE Display::initialize error 4: Renderer does not support PS 3.0.aborting!
•	[2156:12504:1020/225026:ERROR:gl_surface_egl.cc(594)] : eglInitialize D3D9 failed with error EGL_NOT_INITIALIZED
•	[2156:12504:1020/225026:ERROR:angle_platform_impl.cc(33)] : ANGLE Display::initialize error 4: Could not create D3D11 device.
•	[2156:12504:1020/225026:ERROR:gl_surface_egl.cc(594)] : eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type
•	[2156:12504:1020/225027:ERROR:angle_platform_impl.cc(33)] : ANGLE Display::initialize error 4: Renderer does not support PS 3.0.aborting!
•	[2156:12504:1020/225027:ERROR:gl_surface_egl.cc(594)] : eglInitialize D3D9 failed with error EGL_NOT_INITIALIZED
•	[2156:12504:1020/225027:ERROR:gl_surface_win.cc(69)] : GLSurfaceEGL::InitializeOneOff failed.
•	GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
Chrome://flags are also seems to be ok, below are the details
Override software rendering list is enabled
WebGL Draft Extensions  is enabled
Accelerated 2D canvas is enabled
GPU rasterization is enabled
Hardware-accelerated video decode is enabled
WebRTC H.264 software video encoder/decoderis enabled

Under chrome settings: use hardware acceleration is enabled.

Any early response will be highly appreciated.

WebStore page: https://chrome.google.com/webstore/detail/pnacl-examples/mblemkccghnfkjignlmgngmopopifacf

Did this work before? N/A 

Chrome version: 51.0.2704.103  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

This works on some machines with same os but fails on some, mostly gpu details are same as I have provided where its failing.

On machines where its passed and i can see rotating cube following is the chrome://gpu details
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
 
facing similar issue on same configuration machine
Components: -Platform>Extensions Internals>GPU
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Tested this issue in windows 7 and 10 using chrome reported version #51.0.2704.103 and observed that the issue is not reproducible.

Please find attached the gpu details of windows10

Reporter@ - Could you please check this issue on latest stable #54.0.2840.71 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
 
gpu_details_Win10.txt
10.1 KB View Download

Comment 4 by ericrk@chromium.org, Jan 12 2017

Components: -Internals>GPU Platform>NaCl>SDK
Looking at the log messages, it appears that the machine on which the test was failing doesn't support GPU at all. It appears that either there is no GPU installed, or possibly that the GPU is old enough that it doesn't support the minimum pixel shader version (PS3). In these cases, I think a failure of the extension is expected. It's possible that the extension should provide a better error message.

Assigning to NaCl team in case they want to update the extension to provide a better error message (or update the store page to indicate that the extension is not compatible with these devices - not sure if store filtering allows this).
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 13 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment