On the Chrome team we frequently open chromium from the command line (and very very extensively in testing infrastructure) so the most likely cause is something specific to your environment.

Can you confirm that the same command line is being executed when it works and does not work. You can see that in chrome://version

It's also worth trying to find out if all of the system environment variables and exec paths etc are the same. You might simply be failing to load all fonts, for example.

And if you're building Chromium yourself you can presumably build Debug, and see if any DCHECKs hit.

"Can you confirm that the same command line is being executed when it works and does not work"

- Yes can confirm that $SHELL is both /bin/zsh.

"You can see that in chrome://version"
See the attached image a comparison of both showed up it's content is identical.


I can also reproduce this behaviour also by using sh and bash out of IntelliJ (working) and in a separate shell.



I'm using Chromium within the puppeteer (1.3) project and all the issues I actually have.

Just now I've installed puppeteer in an older version (1.0) which ships with Chromium in Version 65.0.3312.0.

There I cannot reproduce the behaviour reported in this issue. It's working entirely as expected. 

Deleted: Bildschirmfoto 2018-04-14 um 12.49.27.png 666 KB

	Bildschirmfoto 2018-04-14 um 12.49.27.png 666 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

The issue seems to be out of TE-scope as it require chromium to be used along with puppeteer (1.3) project. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

Given the chrome://version information is identical, the only reasonable different must be in the OS environment that Chromium is running. It seems that puppeteer would be responsible for that, so I think the bug is on their end.

I suggest you follow up with the Puppeteer group via GitHub.

Meanwhile I'll assign this to the headless chrome team, as that's the closest component we have.

I just mentioned that chromium was installed together with puppeteer but I was able to isolate the issue to the shipped chromium which comes along with puppeteer.

I ran chromium directly out of the puppeteer folder via various terminals and not via the JavaScript api.

Do you have non-English locale with "," decimal separator set?
You may try running with "export LC_NUMERIC=en_US" to check.
If it's true then this problem is fixed in https://chromium-review.googlesource.com/c/1025091/

Can confirm

Using 
> export LC_NUMERIC=en_US

results in a page as expected.


Thank you very much

The NextAction date has arrived: 2018-04-30

Appears to have already been dealt with, according to comment #9.