search

google / latency-benchmark

Tests web browser input latency and jank
http://google.github.io/latency-benchmark
Apache License 2.0
447 stars 44 forks source link

Chrome Canary – "Failed to find test pattern on screen" #3

Open timoxley opened 10 years ago

timoxley commented 10 years ago

Version 33.0.1706.0 Canary OSX 10.9 Retina Display

Tests work fine in regular Chrome.

Fails with 500 error on http://localhost:5578/test?magicPattern=8a36052d02c5645bb97fc46e

Failed to find test pattern on screen. Ensure that your browser's zoom level is set to "100%", and the top-left corner of the window is visible. If you have multiple displays, try moving the browser window to the main display.

Single built-in display. I made sure browser zoom level was set to 100% and the top-left corner is visible.

timoxley commented 10 years ago

Interestingly, if I bump the zoom up to 150%, it works. Perhaps it's a retina issue.

jdarpinian commented 10 years ago

Interesting. I can't reproduce the issue on my retina macbook with the same version of Chrome Canary and OS X. Do you have your retina display set to a "scaled" resolution in system preferences? Which specific retina macbook do you have?

Another thing that can cause this error is if you have your Dock on the left side of the screen and the drop shadow is slightly overlapping the top-left corner of the window. Programs like f.lux or Shades that darken the whole screen could also cause this.

timoxley commented 10 years ago

Retina, 13-inch, Early 2013

I did have it scaled, but tried it non-scaled, still no work.

I have Dock on the side, but it auto-hides, and the window wasn't fully against the side of the screen in each test anyway.

Here's a screenshot:

screen shot 2013-11-12 at 3 07 14 am

timoxley commented 10 years ago

I do have a lot of the chrome experiments enabled. Possible one of them is affecting it.

timoxley commented 10 years ago

Got it. Broken when "experimental Web Platform features" is enabled.

chrome://flags/#enable-experimental-web-platform-features

jdarpinian commented 10 years ago

Cool, thanks for the info! I can reproduce the problem now. I'll bet they changed how devicePixelRatio works or something; I'll look into it.

On Mon, Nov 11, 2013 at 11:22 AM, Tim Oxley notifications@github.comwrote:

Got it. Broken when "experimental Web Platform features" is enabled.

chrome://flags/#enable-experimental-web-platform-features

— Reply to this email directly or view it on GitHubhttps://github.com/google/latency-benchmark/issues/3#issuecomment-28229951 .

k3n commented 10 years ago

I get the same failure, but do not have #enable-experimental-web-platform-features enabled.

Win7x64/30.0.1599.101 m.

jdarpinian commented 10 years ago

Thanks for the report k3n. I've filed a separate issue for Windows multi-monitor problems: issue 5