Comment 3 for bug 965314

I seem to be experiencing a similar issue - Chromium seems to core dump immediately when it loads. Only occassionally it doesn't - I'm actually writing this bug in Firefox as I can't seem to get Chromium to stay up.

I ran Chromium from the command line, and collected some information:

jacobsma@snellebak:~$ chromium-browser
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
[11259:11273:165486117836:ERROR:native_backend_gnome_x.cc(664)] Keyring find failed: Error communicating with gnome-keyring-daemon
[11259:11259:165486445951:ERROR:browser_main_loop.cc(138)] Gdk: IA__gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed
[11259:11259:165486446253:ERROR:browser_main_loop.cc(138)] GLib-GObject: g_object_ref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165487584864:ERROR:browser_main_loop.cc(138)] GLib-GObject: g_object_unref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165527533125:ERROR:x11_util.cc(1121)] X Error detected: serial 27968, error_code 10 (BadAccess (attempt to access private resource denied)), request_code 140, minor_code 1 (X_ShmAttach)
[11259:11259:165527535112:ERROR:x11_util.cc(1121)] X Error detected: serial 27969, error_code 148 (BadShmSeg (invalid shared segment parameter)), request_code 140, minor_code 3 (X_ShmPutImage)
[11259:11259:165527536294:ERROR:x11_util.cc(1121)] X Error detected: serial 28044, error_code 148 (BadShmSeg (invalid shared segment parameter)), request_code 140, minor_code 2 (X_ShmDetach)

>> During this session Chromium stayed up - however I figured perhaps the output was relevant.

Further sessions always result in the same output:

jacobsma@snellebak:~$ chromium-browser
chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed.
Aborted (core dumped)

>> The "cairo" error has been reported in varios other bugs (is it ever going to be fixed??) - and does not seem to be related to this problem as the core happens a fraction of time after the "cairo" error is logged.

I've collected two core dumps and will attach them to this bug report.