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

Issue 670968 link

Starred by 3 users
Status: WontFix
Owner:
█ dongseon...@intel.com
Last visit 21 days ago
Closed: Dec 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Corrupt display visiting vsynctester.com

Reported by jer...@duckware.com, Dec 3 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36

Steps to reproduce the problem:
1. Use r436120 or later
2. if using D3D11, use --disable-d3d11
3. visit vsynctester.com

What is the expected behavior?

What went wrong?
the rendered web page / display is corrupt (see attached)

Did this work before? N/A 

Chrome version: 57.0.2940.0  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

Bisect r436112 works, r436120 fails

https://chromium.googlesource.com/chromium/src/+log/c93085c19a652cd623f44e46ca52f4b10c97233f..8c972de6c3056ddfed390de53e30251e170eddc1

8c972de Increase timeout of JS Injection verification
aa0bf6d media: Add MediaInterfaceProxy
60d375f Reland "Fix HTML5 video blurry"
7fe3856 Added MojoCompositorFrameSink::EvictFrame() and MojoCompositorFrameSinkClient::WillDrawSurface()
07cab68 [Offline Pages] Adds storage for kInvalidOfflineId
62cbfb83 WindowManagerClient::AddAccelerator() should take an array
fe53f36 Re-generate transport_security_state.h
7132d89 image_decoder: Delay shutdown on idle

When run with --disable-gpu-driver-bug-workarounds, Chrome works (changes from Direct3D9Ex to Direct3D11)
badscreen.jpg
218 KB View Download

Comment 1 by jer...@duckware.com, Dec 4 2016 

Run with logging to see lots of GL errors being produced.

Comment 2 by dongseon...@intel.com, Dec 4 2016

Owner: dongseon...@intel.com
Thank you for reporting. I might break it. Could you share the "lots of GL errors"?
Anyway, it's reverted now. https://codereview.chromium.org/2544893006/

Comment 3 by jer...@duckware.com, Dec 5 2016 

 dongseon/2: see attached.

Thank you for reverting.  That fixed things!  You may close this issue.

r436175 fails, but r436176 works -- apparently confirming that the revert fixed the issue.
chrome_debug.log
65.1 KB View Download

Comment 4 by jer...@duckware.com, Dec 5 2016 

dongseon/2: Also, I hope it helps, the problem computer was "System One" at http://www.vsynctester.com/manual.html#testsetup, Intel driver version 8.15.10.2321 -- and then replicated in a more modern Win 8.1 (15 month old) notebook system using "--disable-d3d11".  Hopefully that command line option will allow you to personally also replicate and see the problem.  The 'chrome_debug.log' was created with (and histograms at the end deleted):

  set CHROME_LOG_FILE=(TEMPFOLDER)\chrome_debug.log
  chrome.exe --enable-logging --v=3 --log-gpu-control-list-decisions

Comment 5 by ajha@chromium.org, Dec 5 2016

Labels: M-57
Status: WontFix (was: Unconfirmed)
Closing as per C#3.
►

Sign in to add a comment