Intermittent issue: ERROR:angle_platform_impl.cc(36)] rx::SwapChain11::present(841): Present failed: the D3D11 device was removed, HRESULT: 0x887A0005
Reported by
korrapol...@gmail.com,
Jul 2 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. initiating chromedriver.exe (2.30 version)through protractor scripts. 2. Intermittently seeing the issue 3. Some time a pop up chrome.exe - Application error with software initiation error is coming up but if i OK it, it running further. What is the expected behavior? Should not see the error given in "What went wrong" and over come the pop up. What went wrong? [0702/145023.844:ERROR:angle_platform_impl.cc(36)] rx::SwapChain11::present(841): Present failed: the D3D11 device was removed, HRESULT: 0x887A0005 [0702/145023.848:ERROR:gles2_cmd_decoder.cc(15372)] Context lost because SwapBuffers failed. [0702/145023.850:ERROR:gles2_cmd_decoder.cc(15741)] Onscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR [0702/145023.852:ERROR:gles2_cmd_decoder.cc(5286)] Error: 5 for Command kPostSubBufferCHROMIUM [0702/145023.854:ERROR:gpu_channel_manager.cc(218)] Exiting GPU process because some drivers cannot recover from problems. [0702/145023.856:ERROR:gpu_channel_manager.cc(218)] Exiting GPU process because some drivers cannot recover from problems. [0702/145023.860:ERROR:gpu_channel_manager.cc(218)] Exiting GPU process because some drivers cannot recover from problems. [0702/145023.862:ERROR:gpu_channel_manager.cc(218)] Exiting GPU process because some drivers cannot recover from problems. [0702/145023.864:ERROR:gl_bindings_autogen_gl.cc(12679)] Trying to call glDeleteSync() without current GL context [14:50:24] I/launcher - 0 instance(s) of WebDriver still running Did this work before? N/A Chrome version: 58.0.3029.110 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 26.0 r0
,
Jul 4 2017
Seems this issue related to chrome drivers,could some one from dev team please look into this issue.Adding 'TE-NeedsTriagehelp' label for further investigation. Thanks in advance..!!
,
Jul 4 2017
Pls let me know if any further details needed.
,
Jul 6 2017
,
Jul 6 2017
This could be from a lot of things. Some hitch in the driver, a very slow executing program, or something we're doing incorrectly. Without having any idea of how to reproduce it or the context of what was causing the crash I'm not sure what to do here.
,
Jul 9
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 20
There isn't a lot to go on for this bug. Archiving. Please file a new bug if the issue is reproduced. Thanks. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kochi@chromium.org
, Jul 3 2017