Issue metadata
Sign in to add a comment
|
Recent canvas 2d change breaks vsynctester.com on Windows 7 with old Intel driver (huge frame rate drop)
Reported by
jer...@duckware.com,
Jul 20
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: Visit vsynctester.com and observe frame rate What is the expected behavior? What went wrong? Frame rate is 8 fps (should be 60 fps). Did this work before? Yes Chrome version: 69.0.3497.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: r576611 is good. r576618 is bad. Changes made: 7390498 [Media Intent Handler] Add tests for MediaLauncherActivity by Tommy Steimel a4fe4f7 Move chromeos/system/version_loader -> chromeos/dbus/util by Steven Bennetts d282067 Grant permissions to luci scheduler on Findit's bucket. by Roberto Carrillo ae087c5 Reland "Make TabLoader responsible for loading all tabs." by Chris Hamilton 642db78 Move chromeos/cryptohome/tpm_util -> chromeos/dbus/util by Steven Bennetts a6e1713 Supersize: Fix symbol count bug by Tiger Oakes 79531c7 Make OffscreenCanvas 2d contexts use CanvasResource by Justin Novosad Most likely cause is change by junov
,
Jul 20
Attached is chrome://gpu on problem system using r576618. on problem system, at vsynctester.com, click on gear icon and set "Background images" to "2" MP and stable vsync returns. why is there now such a large performance penalty?
,
Jul 20
I can't repro in the latest builds. I'll do some more digging to find out whether something recently fixed this just in case it needs to be merged to the M69 release branch. There is also a chance that the bug is still reproducible, but only with specific hardware/drivers. @jerryj: your previous comment suggest that you see this problem only on some systems and not on others. Is that correct?
,
Jul 20
junov, correct. problem happens on older Win7 system and does not happen on a newer Win10 system. I sure wish there were a way to go into any running Chrome, and grab a text string to pass along (command line) to Chrome on another computer -- that would *fully* mimic all graphics options/settings/workarounds/etc. For whatever value it is: On the problem system, when I run with --disable-gpu-driver-bug-workarounds, things work.
,
Jul 23
Now something else must have changed. Now the fixes described above no longer work in today's Canary (70.0.3499.1). vsync in Chrome is now 100% broken on this system even with fixes applied (Chrome can only can get to a frame rate of around 47fps). I can only assume that structural things are changing?
,
Jul 25
,
Jul 25
,
Jul 30
Folks, this seems to be related to disable-gpu-driver-bug-workarounds on Win7. Could it be that something that we are disabling makes vsync weird?
,
Jul 30
Submitter: we would need to see about:gpu from Chrome Canary with --disable-gpu-driver-bug-workarounds , where that seems to not be working. But more generally: if it's being reported correctly, the date of the installed graphics driver is 3-6-2011 -- over seven years ago. Chrome continues to evolve to use newer features of graphics drivers, and we can not guarantee that it will work unchanged on such old drivers. What model of computer is this? Is it feasible for you to upgrade to Windows 10? Please provide about:gpu from Chrome Canary with --disable-gpu-driver-bug-workarounds . Downgrading back to P2. This is not a release blocker.
,
Jul 30
,
Jul 30
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by junov@chromium.org
, Jul 20Status: Assigned (was: Unconfirmed)