chromium-browser crashed with SIGSEGV in g_slice_alloc()

[Hasse Bylov]

Just happened... Only five tabs open. No action performed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.79~r125985-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Mon Mar 19 10:54:42 2012
Desktop-Session:
 DESKTOP_SESSION = default
 XDG_CONFIG_DIRS = /etc/xdg/xdg-default:/etc/xdg
 XDG_DATA_DIRS = /usr/share/default:/usr/local/share/:/usr/share/
EcryptfsInUse: Yes
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so\ --lang=en-US\ --channel=11017.0xbcdaac30.840409521
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb37fffa6 <g_slice_alloc+486>: mov (%esi),%edx
 PC (0xb37fffa6) ok
 source "(%esi)" (0x006f732e) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_freeze_notify () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: chromium-browser crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to precise on 2012-03-08 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #926143, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.