Arch Linux

hsz

Member

Registered: 2009-09-25

Posts: 30

Google Chrome issue (Failed to adjust OOM)

After upgrading VirtualBox to 5.0.18 (with guest additions) I have problems with running Google Chrome application:

 ~ $  google-chrome-stable --version
Google Chrome 50.0.2661.75 

 ~ $  google-chrome-stable 
[5960:5960:0420/120442:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
[5960:5988:0420/120442:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6046: Permission denied
[6035:6035:0420/120442:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
[5960:5988:0420/120442:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6052: Permission denied
[5960:5988:0420/120442:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6061: Permission denied
[5960:5988:0420/120443:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6068: Permission denied
[5960:5988:0420/120443:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6103: Permission denied
[5960:5988:0420/120443:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6105: Permission denied
[6035:6035:0420/120444:ERROR:texture_manager.cc(2421)] [.CommandBufferContext.Compositor-0x27c7a1ecb00]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_ENUM : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[5960:5988:0420/120444:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6116: Permission denied
[5960:5988:0420/120444:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6119: Permission denied
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[5960:5988:0420/120444:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 6123: Permission denied
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[6035:6035:0420/120444:ERROR:gles2_cmd_decoder.cc(2134)] [.CommandBufferContext.CompositorWorker-0x27c7a1ecc60]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
...

Do you have any idea, how can we handle it ?

Last edited by hsz (2016-04-20 10:08:05)

triforce

Member

From: United Kingdom

Registered: 2013-07-02

Posts: 12

Website

Re: Google Chrome issue (Failed to adjust OOM)

I had a dig around the VirtualBox open issues and stumbled across this which looks like it might be related. I would subscribe to this issue and in the meantime downgrade the package to a working version.

hsz

Member

Registered: 2009-09-25

Posts: 30

Re: Google Chrome issue (Failed to adjust OOM)

@triforce Disabling the 3D acceleration fixes the problem. Anyway it's just a walkaround. ;-) Thanks for linking this issue !

rbellamy

Member

Registered: 2012-11-30

Posts: 17

Re: Google Chrome issue (Failed to adjust OOM)

Looks like this is a known bug: https://bugs.chromium.org/p/chromium/is … ?id=576409

Fix appears to be in the pipeline as of Feb 17, 2016.

Toet

Member

Registered: 2008-11-22

Posts: 13

Re: Google Chrome issue (Failed to adjust OOM)

Still appears to be a problem at Chromium version 50.0.2661.94. When my analysis is correct, the bug is reported fixed in this version. When I look at the issue 576409, I can see it says: Cr-Commit-Position: refs/heads/master@{#375781}

Looking at https://omahaproxy.appspot.com/ , I can see that the branch_base_position is 378081 for this version. Is this a correct assumption? And if so, what is the correct way to reopen this bug?