On launch, failed to initialize command buffer

Bug #1355588 reported by dino99
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Invalid
Undecided
Unassigned
chromium-browser (Ubuntu)
Invalid
High
Unassigned
Declined for Utopic by Olivier Tilloy

Bug Description

Utopic i386 booted with 'systemd' and logged with gnome-shell

Trying to use the new 36 version, i get the loaded with the blue background 'aie, aie, aie' pages.
The terminal output is:

oem@dev32:~$ chromium-browser
[26025:26059:0812/060307:ERROR:nss_util.cc(853)] After loading Root Certs, loaded==false: NSS error code: -8018
[26025:26059:0812/060308:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060308:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26025:0812/060308:ERROR:gpu_channel_host.cc(146)] GpuChannelHost::CreateViewCommandBuffer failed.
[26025:26025:0812/060308:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer.
[26025:26025:0812/060309:ERROR:gpu_channel_host.cc(146)] GpuChannelHost::CreateViewCommandBuffer failed.
[26025:26025:0812/060309:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer.
[26025:26059:0812/060309:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060309:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26025:0812/060310:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize.
[26025:26025:0812/060310:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed.
[26025:26025:0812/060310:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer.
[26025:26059:0812/060310:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060310:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[26025:26059:0812/060311:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060311:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26059:0812/060311:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060311:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26059:0812/060311:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060311:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26059:0812/060312:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060312:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[26025:26059:0812/060325:ERROR:raw_channel_posix.cc(139)] recvmsg: Connexion ré-initialisée par le correspondant
[26025:26059:0812/060325:ERROR:channel.cc(297)] RawChannel fatal error (type 1)

That is, fully unsuable; please set back the 35 version.

dino99 (9d9)
tags: added: bot-stop-nagging systemd-boot utopic
Revision history for this message
dino99 (9d9) wrote :

hm, get that issue with many url (phoronix.com, tomshardware.fr, ...) but not with others like: planet.ubuntu.com, forexfactory.com.

Revision history for this message
dino99 (9d9) wrote :

Looks like the affected pages are disturbed by the adblock addon: get a notification about it, but not very usefull, as i cant reset chromium to its default (its own page is also affected).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
ubuntu5cto (plusovatel) wrote :

also

ATTENTION: default value of option force_s3tc_enable overridden by environment.
[3953:3981:0812/170312:ERROR:raw_channel_posix.cc(139)] recvmsg: Соединение разорвано другой стороной
[3953:3981:0812/170312:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[3953:3981:0812/170323:ERROR:raw_channel_posix.cc(139)] recvmsg: Соединение разорвано другой стороной

~$ chromium-browser --version
Chromium 36.0.1985.125 Ubuntu 14.10

Revision history for this message
dino99 (9d9) wrote :
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Chad Miller (cmiller)
Revision history for this message
ubuntu5cto (plusovatel) wrote :

chromium 35.0.1916.153-1

https://packages.debian.org/wheezy/chromium

i return old version becouse bug no fix

Revision history for this message
ubuntu5cto (plusovatel) wrote :

but need install also chromium-inspector and libudev0

Martin Pitt (pitti)
tags: removed: systemd-boot
Revision history for this message
Thiago Martins (martinx) wrote :

Hey guys!

It is impossible to use Google Chrome, Chromium or Opera Stable, with Ubuntu 14.10 (64-bit). All the three browsers crashes 10 times per day, same problems.

I just recorded a video while it is crashing, take a look:

http://youtu.be/M0f4CjCuCvg

It might be related to this:

https://code.google.com/p/chromium/issues/detail?id=381732

https://code.google.com/p/chromium/issues/detail?id=415928 -> Merged into 381732

https://bugs.archlinux.org/task/42110

I'm about to manually backport Linux 3.18 from Vivid, into Utopic, to see if it fixes the problem. If it doesn't, I'll try to downgrade it to Chromium 37.

Also, it doesn't matter if I'm running it within Unity, Gnome or Enlightenment DR19, it ALWAYS crashes while browsing the Web.

This problem is very annoying! It is affecting my day job in a very bad way.

Please, let me know if the problem I'm seeing is the same of #1355588, otherwise, I'll fill another bug report.

Best,
Thiago

Revision history for this message
dino99 (9d9) wrote :

hi martinx,

i'm now mainly using Vivid i386 & gnome-shell all the days long. So chromium 39 is the vivid package, and it still has 'sometimes' that irritating 'aie something happened' blue screen. As i can see, that happen while some image's format(s) are loaded by a page, but i can't tell which one(s). I might need to try viewing the 'crashed' page source to find some idea about the format to be blamed. (but it also can be a false positive investigation on my own)

ps: backporting from vivid might not help sadly.

Revision history for this message
Thiago Martins (martinx) wrote :

Hi dino99!

 You was right, upgrading my kernel do 3.18 did not helped...

 Nevertheless, I disabled the Chromium option couple days ago:

 [ ] Use hardware acceleration when available

 ...and I'm running it for about two days without a single crash! Hope it remains stable from now on...

Cheers!
Thiago

Revision history for this message
dino99 (9d9) wrote :

hi martinx,

thanks for pointing the 'hardware acceleration' setting: was enabled , so i've turned it off then restarted chromium. But that issue was still happening when watching a known url (tomshardware) giving that 'bluescreen of the death' a bit too often.

and i think having found what is giving that problem:
- the 'adblock' plugin is installed , so i've checked its 'filter lists' options:
- inside 'other filter lists' i've disabled 'antisocial filter list'

and then going back to a tomshardware page that was always crashing, after that option disabled, i get no more 'bluescreen' page crash.

so as i can see right now, if the 'antisocial filter list' is enabled, then that issue appear.

Revision history for this message
dino99 (9d9) wrote :

well there are some other troubles, like some embebded video loading then crashing before they are fully loaded

Revision history for this message
dino99 (9d9) wrote :

Feedback about the latest #11 setting tweak:

- continue to get that 'bluescreen' message, even with the 'social' icons enabled (chromium default)
- maybe the real reason is that the time needed to load the page (with all the embedded objects: image, advertise, ...) is too long, compared to what chromium expect.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Chad Miller:

Because this bug does not render the system unusable, it does not have an importance of "critical".

summary: - Failed to initialize command buffer
+ Failed to initialize command buffer on launch
summary: - Failed to initialize command buffer on launch
+ On launch, failed to initialize command buffer
Changed in chromium-browser (Ubuntu):
importance: Critical → High
Changed in chromium-browser (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
dino99 (9d9) wrote :

Way better since chromium 40 has been upgraded on Vivid : i was having the "aw, snap!!" fatal blue screen so often on "tomshardware" site, but now that does not happen since a couple weeks.

Revision history for this message
dino99 (9d9) wrote :

Closing that report now , as:
- utopic support has now ended
- chromium version is now more recent
- that issue has not been met recently

Changed in chromium-browser (Ubuntu):
status: Triaged → Invalid
dino99 (9d9)
Changed in chromium-browser:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
assignee: Chad Miller (cmiller) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.