It looks like you're getting some program linking options. We've seen problems in the past with the way the shader generator interacts with system locale. Two questions:

- What locale is your system running (is it using one where the decimal separator is ","? - for example, 756,34)
- Are you launching Chrome from the command line?

OK, I can repro. It appears to have to do with system locale. The minimum repro steps seem to be:

1. Open a command prompt.
2. run "export LC_NUMERIC=de_DE.UTF-8" (or another locale with non-"," decimal separator)
3. Run Chrome from the command prompt

This seems to be a case of  issue 666228  popping up again - so maybe the previous fix missed something? Can you take a look?

 Issue 698609  has been merged into this issue.

Bumping to P1 as we've gotten a few reports of this.

I'll take a look. I may have an odd locale indeed.

Re: #1: Indeed, I was running chrome from command line, and the system locale was ru_RU.UTF-8.

I have a fix in progress, thanks for all the reports / info.

The following revision refers to this bug:
  https://skia.googlesource.com/skia/+/0d2c9a252e0f113a70842280d0ef7190a062fa89

commit 0d2c9a252e0f113a70842280d0ef7190a062fa89
Author: Eric Karl <ericrk@chromium.org>
Date: Mon Apr 17 20:04:47 2017

Pass LC_ALL_MASK to newlocale

This change fixes an issue with GrAutoLocaleSetter, which was
using the C library LC_ALL mask with newlocale. Instead the
xlocale LC_ALL_MASK should be used (these do not match on all
platforms).

See: http://man7.org/linux/man-pages/man3/newlocale.3.html

Bug:  711683 
Change-Id: I6dba140e72b095f75667f0dcc98480d8d4562191
Reviewed-on: https://skia-review.googlesource.com/13601
Reviewed-by: Ethan Nicholas <ethannicholas@google.com>
Commit-Queue: Ethan Nicholas <ethannicholas@google.com>

[modify] https://crrev.com/0d2c9a252e0f113a70842280d0ef7190a062fa89/src/gpu/GrAutoLocaleSetter.h

This bug requires manual review: We are only 7 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I've just also noticed the following: the problem manifests itself only when I have an external monitor connected (running in 1920x1080@2 Retina, 50 Hz). My MacBook Pro has two graphics cards, and possibly in dual monitor mode the Mac uses the oj-board Intel card. When the monitor is disconnected and only the built in display is used with the NVIDIA card, the problem does not seem to appear.

Sounds like it's too late for M58. We'll let this roll out through M59.

Update - I missed the M59 branch without realizing it - this will roll out through M60.

 Issue 713290  has been merged into this issue.

 Issue 710274  has been merged into this issue.