Errors when starting Chromium from console
Reported by
stu...@anchev.net,
Feb 16 2018
|
||
Issue description
Chrome Version : 64.0.3282.167
OS Version:
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1.
[~]: chromium --password-store=gnome --disk-cache-dir=/home/myusername/.cache/chromium --disk-cache-size=104857600 --show-component-extension-options --force-device-scale-factor=1.2
What is the expected result?
No errors.
What happens instead of that?
-------------
[5364:5393:0217/002917.705535:ERROR:nss_util.cc(724)] After loading Root Certs, loaded==false: NSS error code: -8018
[5364:5364:0217/002917.715892:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: NTPContentSuggestionsEnabled
[1:18:0217/002920.641622:ERROR:adm_helpers.cc(73)] Failed to query stereo recording
-------------
Please provide any additional information below. Attach a screenshot if
possible.
I also notice that sometimes when I open a new blank tab and then I click to close it in console I see the following messages:
-------------
[5437:5437:0217/003953.292620:ERROR:gles2_cmd_decoder.cc(18162)] [.DisplayCompositor-0x91420959c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[5437:5437:0217/003953.292665:ERROR:gles2_cmd_decoder.cc(10008)] [.DisplayCompositor-0x91420959c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5437:5437:0217/003953.292702:ERROR:gles2_cmd_decoder.cc(18162)] [.DisplayCompositor-0x91420959c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[5437:5437:0217/003953.292729:ERROR:gles2_cmd_decoder.cc(10008)] [.DisplayCompositor-0x91420959c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
-------------
I don't know if those are in any way related or should go into a separate bug report. Please let me know.
FWIW: /home/myusername/.cache/chromium is on tmpfs and there is plenty if space on it (many gigabytes).
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
,
Feb 19 2018
Unable to reproduce this issue on reported version 64.0.3282.167 using Ubuntu 14.04 with below steps. 1. Launched chromium with below URL chromium-browser --password-store=gnome --disk-cache-dir=/home/myusername/.cache/chromium --disk-cache-size=104857600 --show-component-extension-options --force-device-scale-factor=1.2 2. Browser launched successfully without any errors in console or terminal. Tentatively adding Internals>Installers component. Could someone from dev team please have a look at errors mentioned in comment#0. Thanks!
,
Feb 19 2018
Additional info: I also have: chrome://flags/#ignore-gpu-blacklist = enabled chrome://flags/#shared-array-buffer = disabled chrome://flags/#enable-site-per-process = enabled Additionally disabled: chrome://settings/content/cookies chrome://settings/content/location chrome://settings/content/camera chrome://settings/content/microphone chrome://settings/content/notifications chrome://settings/content/javascript chrome://settings/content/flash chrome://settings/content/backgroundSync chrome://settings/content/automaticDownloads chrome://settings/content/unsandboxedPlugins chrome://settings/content/midiDevices chrome://settings/content/protectedContent chrome://settings/languages chrome://settings/cloudPrinters The videocard is GTX 680 [~]: rpm -q nvidia-glG04 nvidia-glG04-390.25-10.1.x86_64 Testing on openSUSE Leap 42.3 with Plasma 5.8.7 |
||
►
Sign in to add a comment |
||
Comment 1 by krajshree@chromium.org
, Feb 18 2018