Graphics corruption on Pixel 2015 |
|||||||
Issue descriptionVersion: 49.0.2623.111 OS: Chrome_ChromeOS After my Pixel 2015 has been running for a while, it sometimes shows significant graphics corruption across the entire display, mixing blocks from old and new tabs and failing to paint menus. The tab strip and omnibox are most affected (mixing parts of tabs and URLs from different windows), as are the system menu in the lower right and the search key menu (neither of which finish painting). Screenshots attached. The machine is basically unusable when this happens, and I have to restart it. I have to use the power button to do so since the system menu is unusable. I've seen this happen immediately after a restart, too, so it's not specific to a long running session. I do, however, have lots of tabs and windows open, so that may be involved. (Just restarted into M50, so I'm not sure if it will happen here or not.)
,
May 11 2016
Looks like you are running CrOS M49 build. You have a pending update waiting for restart. Could you restart and see if this problem is reproducible?
,
May 11 2016
,
May 11 2016
I restricted the issue for privacy reasons (screenshots). Looks like one of the file descriptor issues. If you run into this again please file a feedback report and post the id.
,
May 11 2016
I'm battling issue 611127 after restarting into M50, but I'll try to send a feedback report if it happens again. How do I find the feedback ID once I file it? (Note to self: Alt+Shift+I is the shortcut for sending feedback, since the menu item for "Report an issue" won't paint if the bug happens again.) FWIW, this has been happening to me about once a week for the past month. I was finally able to capture screenshots to file the bug.
,
May 11 2016
You could just leave a code word in the description. It makes it easier to find. Silly, I know.
,
May 11 2016
Yes it looks like the fd problem we had before. If you're still on 49, please try to let it go to 50 first.
,
May 11 2016
Yes, I'm on M50 now, though it's unusable now because of issue 611127 . Still, I'll send feedback if it happens again. For reference, can you post a link to the bug for the fd problem?
,
May 11 2016
There were several. Like issue 582143 or issue 597287 .
,
May 13 2016
Related to Issue 608024 ?
,
May 27 2016
I just hit this bug again in 50.0.2661.104, shortly after rebooting and restoring a large number of tabs. I filed a feedback report, which you should be able to find by searching for either "https://crbug.com/611120" or "ihf@". (It didn't give me an ID to reference.)
,
May 27 2016
Attempting to upload a screenshot from the affected device.
,
May 27 2016
In the screenshot in comment 12, note the following: 1) Right side of tab strip shows a different window's tabs. 2) Address bar is split between two URLs at the same point. 3) Neither half of address bar matches the visible page (chrome://version). 4) Omnibox dropdown is partially visible. 5) Clock is missing. In this state, menus don't draw. Machine is unusable once it starts happening.
,
May 27 2016
This is the report, I am taking a look. https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReport=9305330496
,
May 27 2016
I don't have access (anymore?) to the detailed system logs. From what I can see memory is a bit low, but no zram used. But gtt total at 2^32 is fishy. 915_gem_objects 4926 objects, 2344148992 bytes 4359 [658] objects, 2255228928 [233525248] bytes in gtt 75 [7] active objects, 52781056 [35446784] bytes 4284 [651] inactive objects, 2202447872 [198078464] bytes 69 unbound objects, 9039872 bytes 20 purgeable objects, 1245184 bytes 12 pinned mappable objects, 35663872 bytes 134 fault mappable objects, 32731136 bytes 4294967296 [268435456] gtt total MemTotal: 16345812 kB MemFree: 2105944 kB MemAvailable: 3523872 kB
,
May 27 2016
That was just the total size. I got the logs. There are about 90 tabs/extensions. Heavy use, but should not be out of resources that I can detect. There is an unrelated crash in the logs. https://crash.corp.google.com/browse?stbtiq=0ddf639c00000000
,
May 27 2016
Yep, judging from the time of that crash report, that was the one that made me restart and restore all my tabs, shortly before the bug occurred (see comment 11).
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 13 2018
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 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by creis@chromium.org
, May 11 2016