chromium-browser crashed with SIGSEGV in BrowserContextKeyedServiceFactory::GetServiceForBrowserContext()

[Karma Dorje]

the browser just suddenly stop responding to mouse and keyboard; just closed your window — crashed.

apt-cache policy chromium-browser
chromium-browser:
  Installed: 34.0.1847.116-0ubuntu2
  Candidate: 34.0.1847.116-0ubuntu2
  Version table:
 *** 34.0.1847.116-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
Uname: Linux 3.14.0-999-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 16 03:34:37 2014
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Disassembly: => 0x0: Cannot access memory at address 0x0
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2012-09-30 (562 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1)
ProcCmdline: chromium-browser\ --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ --ppapi-flash-version=12.0.0.77\ --enable-pinch
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 BrowserContextKeyedServiceFactory::GetServiceForBrowserContext(content::BrowserContext*, bool) () from /usr/lib/chromium-browser/libs/libbrowser_context_keyed_service.so
 ?? ()
 ?? ()
 base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
Title: chromium-browser crashed with SIGSEGV in BrowserContextKeyedServiceFactory::GetServiceForBrowserContext()
UpgradeStatus: Upgraded to trusty on 2013-11-10 (156 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
gconf-keys: /desktop/gnome/applications/browser/exec = b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command = b'/opt/google/chrome/google-chrome %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/opt/google/chrome/google-chrome %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-03-23T05:34:43.487383

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 BrowserContextKeyedServiceFactory::GetServiceForBrowserContext (this=0x7fcae846bfa8 <_ZN10extensionsL9g_factoryE+8>, context=0x7fcaea080840, create=<optimized out>) at ../../components/browser_context_keyed_service/browser_context_keyed_service_factory.cc:65
 ChromeRenderMessageFilter::OpenChannelToExtensionOnUIThread (this=<optimized out>, source_process_id=20, source_routing_id=2, receiver_port_id=377, info=..., channel_name=..., include_tls_channel_id=false) at ../../chrome/browser/renderer_host/chrome_render_message_filter.cc:265
 Run (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a6=<optimized out>, a5=..., a4=..., object=<optimized out>, this=<synthetic pointer>) at ../../base/bind_internal.h:530
 MakeItSo (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a7=<optimized out>, a6=..., a5=..., runnable=...) at ../../base/bind_internal.h:1065

[Launchpad Janitor (janitor)]

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

[Olivier Tilloy (osomon)]

Closing now as this report wasn’t investigated timely and is now too old to be meaningful.
Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner.