Chromium called with multiple threads in process gpu-process

cooker
omlx-4
Tags: #<Tag:0x00007fabd7047718> #<Tag:0x00007fabd7047588>

(Ben Bullard) #1

Post-edit: System is hardware installed from ISO 2416 and fully updated.

Chromium seems ruined. Every time I open it there are multiple threads of something opened. Here’s cli output:

$ chromium-browser-stable

(chromium-browser-stable:10733): Gtk-WARNING **: 19:05:01.924: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium-browser-stable:10733): Gtk-WARNING **: 19:05:01.924: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium-browser-stable:10733): Gtk-WARNING **: 19:05:01.924: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
[10763:10763:0226/190502.063043:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
[10733:10798:0226/190527.113620:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[1:1:0226/190640.568367:ERROR:audio_context.cc(52)] Create
[1:1:0226/190640.568464:ERROR:audio_context.cc(130)] AudioContext
[1:1:0226/190640.568575:ERROR:audio_context.cc(146)] document user activation
[1:1:0226/190640.569482:ERROR:audio_context.cc(436)] IsAllowedToStart
[1:1:0226/190640.666175:ERROR:audio_context.cc(52)] Create
[1:1:0226/190640.666276:ERROR:audio_context.cc(130)] AudioContext
[1:1:0226/190640.666306:ERROR:audio_context.cc(146)] document user activation
[1:1:0226/190640.666967:ERROR:audio_context.cc(436)] IsAllowedToStart
[1:1:0226/190641.426304:ERROR:audio_context.cc(52)] Create
[1:1:0226/190641.426385:ERROR:audio_context.cc(130)] AudioContext
[1:1:0226/190641.426412:ERROR:audio_context.cc(146)] document user activation
[1:1:0226/190641.427244:ERROR:audio_context.cc(436)] IsAllowedToStart
libx265.so.169: cannot open shared object file: Operation not permitted
libx265.so.169 is missing, x265 support will be disabled
[1:17:0226/190719.870009:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.870091:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.870124:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.870908:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.870947:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.870974:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.881898:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.881978:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.882018:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.882049:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.882078:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.882105:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[1:17:0226/190719.892939:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:35678 (any)
[1:17:0226/190719.893069:ERROR:stunport.cc(92)] Binding request timed out from 0.0.0.x:38269 (any)
[10733:10733:0226/191303.263944:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()

Here’s a screen shot of KSysGuard showing a page full (there are more actually) of nothing but chrome things using memory and cpu:

First, before I file a bug report, I’d like to know if other users are seeing this behavior? And second I’d like to know what the heck fire is causing this behavior?

Also for a bug report if there are any other logs that might be helpful let me know.


#2

Many processes in Chrome / Chromium are quite normal. For me after opening browser, I have about 8-9 process. After opening new pages or cards I have it even more.
Why? Because Chrome tries to separate contents of each card, each add-on, extension, etc. from the main browser processes. So that the failure one of them did not cause the entire browser to hang completely but only one of its cards.

Here more details:


(Ben Bullard) #3

Thanks, that explains the multiple processes.

It does not explain why Chromium is taking so long to open which contributes to the feeling that something is wrong with Chromium. (Long time to open is in this instance 25 seconds or more.)

Post-edit: So I’m guessing that if it is OK that chromium takes 25 seconds to open then there is nothing that I can identify wrong with Chromium.


#4

I do not know. For me, Chromium starts faster than in 25 seconds, but startup times can depend on hardware.

You can do this:
Download Chromium from the official distribution, unpack it and launch. Then check how long it starts. If the start time is similar, then everything is ok.

https://download-chromium.appspot.com/

EDIT: This build it is in the dev version and does not have any proprietary components like the h264 codec.


(Ben Bullard) closed #5