ERROR:CONSOLE and other messages
Reported by
jongran...@gmail.com,
Aug 27 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Steps to reproduce the problem: 1. jonny@ubuntu1404:~$ /usr/bin/google-chrome \ > --user-data-dir="$HOME/chrome-with-proxy" \ > --proxy-server="socks5://localhost:8080" What is the expected behavior? No error output What went wrong? [22984:22984:0827/234223.384797:ERROR:CONSOLE(1)] "Uncaught ReferenceError: inline is not defined", source: (1) [22984:23018:0827/234324.211500:ERROR:service_manager.cc(142)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser [24593:24593:0827/234324.290513:ERROR:ppapi_thread.cc(333)] Failed to load Pepper module from internal-not-yet-present (error: internal-not-yet-present: cannot open shared object file: No such file or directory) Did this work before? N/A Chrome version: 60.0.3112.101 Channel: n/a OS Version: Flash Version:
,
Aug 29 2017
Hi Hdodda Do you have another GNU-Linux machine? Just run ssh to your other machine ssh -C -D localhost:8080 ubuntu@host Then launch chrome: /usr/bin/google-chrome \ --user-data-dir="$HOME/chrome-with-proxy" \ --proxy-server="socks5://localhost:8080"
,
Feb 11 2018
These aren't fatal errors. If you want to you pipe stdout/stderr to dev/null on launch.
,
Feb 12 2018
It's surprising the defect is not being taken seriously. Why not fix defects? |
||
►
Sign in to add a comment |
||
Comment 1 by hdodda@chromium.org
, Aug 29 2017Labels: Needs-Triage-M60 TE-NeedsTriageHelp