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

Issue 719340 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Severe UI redraw problems since 58

Reported by mrva...@gmail.com, May 8 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Upgrade 57 to 58 
2. Open Chrome, resize window

What is the expected behavior?
Resized window, correctly redrawn UI

What went wrong?
Resized window, unusable UI

Did this work before? Yes 57

Chrome version: 58.0.3029.96  Channel: stable
OS Version: Zesty
Flash Version: 

intel i915 GPU.
Flags all default does not solve the problem.
 

Comment 1 by mrva...@gmail.com, May 8 2017

Little video showing the repaint issue.
Chrome_RepaintIssue.ogv
1.5 MB View Download
Labels: Needs-Triage-M58
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce this issue on Ubuntu 14.04 (intel core i7) using chrome latest stable M58-58.0.3029.96. No rendering issue is observed in chrome while resizing the browser.

mrvanes@ Are you able to reproduce this issue consistently including incognito mode? Please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser.

Thanks!

Comment 4 by mrva...@gmail.com, May 15 2017

Yes, unfortunately I can reliably reproduce this issue on M58-58.0.3029.110, both normal and incognito mode and using a freshly created profile.

Like I said, I'm on Zesty not Trusty, using a custom built vanilla kernel 4.11.1 and most up-to-date official intel drivers from https://www.01.org/. Zesty is on Xorg 7.7, MESA 17.0.3 and I enabled DRI3 in xorg.conf. Attached output of glxinfo.txt.

If you need more info, I'd be glad to supply.
glxinfo.txt
24.8 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, May 15 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 6 by hdodda@chromium.org, May 17 2017

Labels: TE-Hardware-Dependency TE-NeedsTriageFromMTV
@MTV Team-- Routing to MTV team , could someone please look into this , as Inhouse-HYD team doesn't have the mentioned hardware .

Thanks!

Comment 7 by mrva...@gmail.com, Jun 7 2017

Chrome 59.0.3071 still exhibits the same problem.

Comment 8 by mrva...@gmail.com, Jun 8 2017

Solved.
This was a problem on my side I must confess. I had a long standing --disable-gpu-driver-bug-workarounds option set in google chrome desktop file that reared it's ugly head in 58. Removed the option and all's well again!
Project Member

Comment 9 by sheriffbot@chromium.org, Jun 8 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