Issue metadata
Sign in to add a comment
|
renderer warnings and GL errors started showing up for no reason
Reported by
mirek.k...@gmail.com,
Oct 16 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 Steps to reproduce the problem: simply browsing the web for a while causes errors to show up in chrome://gpu What is the expected behavior? no errors What went wrong? no idea. regression, probably. seems to be a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=481398 Did this work before? Yes i'm honestly not sure, i'm not lurking into chrome://gpu that often. possibly before the last update, but i could be very wrong in that regard. Chrome version: 54.0.2840.59 Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: disabled
,
Oct 18 2016
Could you please provide the sample browsing URL's which causes error in chrome://gpu will help us to triage the issue further. @kbr Could you please confirm this issue related to # 481398. Thank you!
,
Oct 19 2016
it's kinda hard to pinpoint. i've just tried, after restarting chrome, and all the usual and less usual activity, like secure shell, browsing few sites, playing youtube videos, including closing the tab mid-playback, did nothing. it could be random, i never really noticed that something is wrong, other than those messages in gpu log. and the hang a few minutes ago, that forced me to kill the browser. it just stopped responding, entirely, including secure shell windows. no unusual activity, just a short clip on youtube and 3 other tabs with no multimedia activity - or activity of any kind - whatsoever. if you have any ideas/website-to-test suggestions, let me know. just to be clear, i'm never using webgl - it isn't really working on this dx9 gpu - and i've got flash player disabled. rasterization - as seen in the log - is done on the cpu, since when i'll try to force it to run on the gpu, some websites - like google's inbox - have rendering errors. i guess that nails it down to compositing, more or less.
,
Oct 19 2016
CC'ing others who have been investigating other, similar, GPU process issues on older hardware.
,
Oct 24 2016
happening under 55.0.2883.21 as well. still couldn't pinpoint it, it seems kinda random, or just very specific websites trigger it and after all i'm not refreshing gpu log everytime i visit some place. after restart mentioned earlier i didn't restart chrome for days and didn't notice any errors whatsoever. yesterday - i think it was yesterday - i've restarted it to update it, few hours of usage later - errors.
,
Oct 24 2016
this is something new i think: [5828:1640:1024/202628:ERROR:gles2_cmd_decoder.cc(4909)] : GLES2DecoderImpl::ResizeOffscreenFramebuffer failed to allocate storage for offscreen target depth buffer. [5828:1640:1024/202628:ERROR:gles2_cmd_decoder.cc(3292)] : Could not allocate offscreen buffer storage. happened after window resize i think. i wasn't opening anything new at that moment, 4 secure shell windows, 3 tabs, 2 of them were opened for the last few days at least, third one - active one - was newtab (default, no addon). i have a feeling those errors aren't connected to any particular website at all. secure shell windows aren't maximized, browser was before the resize. if i'll notice any new errors, i'll try to corelate them with any possible events/browsing history.
,
Nov 1 2016
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 27 2016
Tested in chrome Beta #56.0.2924.28 and canary #57.0.2963.0 on win 10.0 and not able to reproduce the issue.Please find the screen shots for your reference. @mirek.kaim: Could you please upgrade to latest version and create new profile, recheck once and let us know the observations which would help us to triage the issue further. Thanks in Advance.
,
Dec 27 2016
rechecking once will do nothing. it's entirely random, connected to events like browser window resize rather than some particular website. i'm 100% certain it was happening on previous beta, not sure about current one. i'm looking at gpu logs once every few days, since even when it happens, it has no influence whatsoever on anything, so my assumption is this still happens. you would probably need to use it for few hours on older dx9 gpu like i've got, preferably ati with same catalyst version, to see it. also, i've posted the logs. if you're expecting me to post the screenshots for those - which i didn't take at a time - the question is, what's the point? when i'll notice it again, i'll take a screenshot this time, but it may take a few days. as i've said, it's random, and i've got enough on my plate as it is to not have time to stress test the browser UI for few hours hoping to catch it.
,
Jan 4 2017
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 2 2017
Tested in chrome Stable #56.0.2924.87 Beta #57.0.2987.88 and canary #58.0.3027.0 on win 10.0& 7 and not able to reproduce the issue.Please find the screen shots for your reference. @mirek.kaim: Could you please upgrade to latest version and create new profile, recheck once and let us know the observations which would help us to triage the issue further. Thanks in Advance.
,
Mar 2 2017
We recently fixed an issue with the "GLES2DecoderImpl::ResizeOffscreenFramebuffer failed to allocate storage" error, it probably went into 56 or so. Otherwise the error simply means that the GPU ran out of memory when trying to allocate new buffers. I think this should be WontFix unless there is a reliable way to reproduce because in this case it looks like the GPU process is doing the right thing. Thanks for the report, the feedback is helpful. If you see it happening constantly, re-open the bug. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by durga.behera@chromium.org
, Oct 17 2016