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

Issue 465356 link

Starred by 5 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2015
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

VSYNC is broken in Canary until app window is resized (Win7 D3D9)

Reported by, Mar 9 2015

Issue description

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

Steps to reproduce the problem:
Under Win7, run Canary non-maximized, and do NOT resize app window -- and visit

What is the expected behavior?

What went wrong?
VSYNC in Canary is busted -- until the app window is resized, and then all of sudden, VSYNC starts to work.

Did this work before? N/A 

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

Video of what I see:

Comment 1 Deleted

Unable to repro this issue on windows7 using latest canary: 43.0.2329.0. 

VSYNC is started working properly. Please find the attached screen-cast as reference.

Could you please upgrade to latest canary and re-check this issue.
If issue is still exists, please provide chrome://gpu will help in reproduce.

2.7 MB Download

Comment 3 by, Mar 12 2015

Yes, still happens even in 43.0.2329.0.  YOU CAN NOT USE TABS.  Screen captures interfere, you must use actual video of the screen.

1) close all tabs
2) make sure Chrome is not maximized.
3) close Chrome
4) run Chrome
5) click in omnibox, type "", enter
6) VSYNC will flicker with red/cyan, a FAILURE
7) resize Chrome
8) VSYNC has no color flicker, success

See issue 422000
Labels: -Needs-Feedback Cr-Blink
Status: Untriaged
Able to repro this issue on Windows7 using latest canary: 43.0.2329.0 and latest stable: 41.0.2272.89.

VSYNC is flickering with red/cyan. 

This is non-regression issue, same behavior is observed from M32.

Comment 5 by, Apr 14 2015

This issue seems related to *not* using D3D11, so use --disable-d3d11 to replicate.

Comment 6 by, Apr 14 2015

Labels: -M-43 M-44 MovedFrom-43
[AUTO] Moving all non essential bugs to the next Milestone.  (This decision is based on the labels attached to your ticket.)

Status: WontFix
Summary: VSYNC is broken in Canary until app window is resized (Win7 D3D9) (was: VSYNC is broken in Canary until app window is resized (Win7))
Chrome in D3D9 mode does not use vsync at all. I don't know why vsync would start working after a window resize - it's definitely an unintended consequence. I think it's unlikely that we'll ever fix this. Please feel free to reopen this bug if this affects D3D11. NOTE: It is possible that on some machines (based on a GPU blacklist) for chrome to use D3D9 even when it's not launched with the --disable-d3d11 flag - please look at chrome://gpu to check if you're using D3D9 or D3D11 in the "GL Renderer" field.
This issue has now finally been FIXED -- by the code fix for  issue 632785  (same issue replicated against D3D11).

Chrome in D3D9 mode does VSYNC just fine now (it always did after resizing the Chrome app -- only now, Chrome starts up VSYNCing just fine without the need to resize the app window).

+jbauman as fyi.

Sign in to add a comment