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

Issue 632785 link

Starred by 10 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

issue 422000

Sign in to add a comment

Direct3D11/GPU is not properly initialized until Chrome app window is resized?

Reported by, Jul 29 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36

Steps to reproduce the problem:
0. find a Win7 / Intel HD graphics system (I used Intel 4400)
2. visit
3. notice vsync graph is 'flat', but vsync word indicator flickers (vsync failure)
4. notice input lag indicator shows 1 frame of input lag

5. resize the chrome app window

6. notice that vsync graph now has spikes (still flickers failure like before)
7. notice input lag indicator now shows 2 frames of input lag

What is the expected behavior?
Chrome should not change behavior, simply because the app window is resized

What went wrong?
There appears to be some initialization problem, until the Chrome window is resized.

Did this work before? N/A 

Chrome version: 54.0.2811.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

most likely related to  issue 465356 , but now seen with Direct3D11

Comment 1 by, Jul 30 2016

In steps above, insert this step:

2.5: click gear icon, uncheck 'preview' under 'background image', click gear icon
Components: Internals>GPU
Labels: M-54 Needs-Feedback
Have attached a screen shot of the page following above steps on Win 7 using canary 54.0.2815.0,and cced the dev from the above reference(www. ) to further update on this.
459 KB View Download
durga.behera/2, what was the input lag you noticed as you moved the mouse around?

Attached is what I see on another system, a Dell Inspiron with Intel HD 5500 graphics.
115 KB View Download
118 KB View Download
Blocking: 422000
Project Member

Comment 5 by, Aug 2 2016

The following revision refers to this bug:

commit cb571e2230c90eec7d7c498f6dfd293eaa350001
Author: jbauman <>
Date: Tue Aug 02 23:19:09 2016

Update vsync override in PostSubBuffers.

This was only happening in SwapBuffers, so the vsync override could
become stale if only PostSubBuffers were happening.

BUG= 632785 

Cr-Commit-Position: refs/heads/master@{#409376}


jbauman, thanks!  Looks fixed.  Will test more extensively tomorrow.
Tested Canary 54.0.2817.0 r409416 on three systems.  All worked.  Can mark this issue as fixed.
Status: Fixed (was: Unconfirmed)
The fix for this issue breaks --disable-gpu-vsync.  See  issue 480361 .

Sign in to add a comment