Embedded GIFs/videos on many websites causing Chrome to fall over with NV 4xx series drivers
Reported by
jez2...@gmail.com,
Dec 18
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Example URL: Steps to reproduce the problem: 1. NVIDIA SLI/Surround based system running clean install of Windows 10 1809 x64 2. NVIDIA 4xx series driver 3. Chrome 70/71 4. Webpage with an embedded GIF/video/animation/webm What is the expected behavior? What went wrong? Firstly, I'm unsure whether this is a Chrome specific issue or an NVIDIA driver related issue. With any NVIDIA 4xx series driver installed, on my SLI+Surround based system, a Chrome tab which contains an embedded GIF/animation will randomly go black and freeze for about 1-2 seconds, and then recover, however the GIF is replaced with a green box that looks like the hardware overlay has somehow fallen over. NV version 399.24 is the latest version I have found to be stable with Chrome in this environment. Any 4xx driver I have tested beyond causes this issue and is very easy to reproduce, it often only takes a couple of seconds until the tab "falls over" and then recovers as described above. I have tried a clean installation of Windows 10 latest, only installing a 4xx series driver, enabling Surround, and then installing Chrome 71. The same issue occurs. Thank you and I hope this makes sense Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 71.0.3578.98 Channel: stable OS Version: 10.0 Flash Version:
,
Dec 19
,
Dec 21
jez250a@ Thanks for the issue. Request you to provide a sample URL where this issue can be reproduced, which will help in further triaging of the issue. Thanks..
,
Dec 21
Hi Opening various GIFs from this subreddit (https://www.reddit.com/r/SplitDepthGIFS/) will often trigger it. Sometimes it happens almost straight away, sometimes it may take a minute or two. Another site that often triggers it when there are videos visible on the page: https://www.dailymail.co.uk/home/index.html Thanks again
,
Dec 21
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 15
Hi I tested the latest 417.71 today with the same problem seen. Attached GPU error log. The only current workaround I know of is to either revert to 3xx series drivers or to disable hardware-accelerated video decode in Chrome flags. Thanks
,
Jan 18
(4 days ago)
Diasbling GPU video decode resolves it, so sounds like it's a problem there.
,
Jan 18
(4 days ago)
The logs look like maybe the gpu video decode code is not recovering from a context loss.
,
Jan 18
(4 days ago)
,
Jan 18
(4 days ago)
GPU video decode does not recover from context loss. The current expectation is that decoding will fail (DECODE_ERROR), and then playback can be resumed by pressing 'play' again (assuming there is a play button to press in the particular player). Historically software decode was able to recover by re-uploading frames but this isn't true anymore since the GpuMemoryBuffers are also lost. (However decoding continues and future uploads succeed, so the graphical corruption is temporary in this case.) We have a mechanism for restarting video decoding now, but have not yet determined whether it should be used to recover from context loss. The big question here is, 'Why is the context being lost?'
,
Jan 19
(4 days ago)
[1556:12172:0115/093146.312:ERROR:gles2_cmd_decoder.cc(16124)] : Offscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR [1556:12172:0115/093146.312:ERROR:gles2_cmd_decoder.cc(4583)] : GLES2DecoderImpl: Context reset detected after MakeCurrent. If i remember, all robustness failures cause the gpu process to exit rather than try to recover. given the timing, i assume that this is the cause: "testDeviceLost(1850): The D3D11 device was removed, HRESULT: 0x887A0006". that HRESULT is DXGI_ERROR_DEVICE_HUNG. This might be a good place to try the d3d11 decoder and see what happens. unfortunately, there's not an easy way to enable it except via the command line. i'll add an entry to chrome://flags. Once that gets to canary, it would be interesting to give it a try to see if the problem still happens. +tmathmeyer FYI
,
Yesterday
(46 hours ago)
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Dec 18