chromium-browser crashed with SIGSEGV in freelist_alloc()

Bug #957260 reported by C de-Avillez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Opening a webex session

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.79~r125985-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 16 13:00:45 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
EcryptfsInUse: Yes
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so\ --lang=en-US\ --channel=8291.0x7f9ae93d4320.1710616053
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7ff076586410 <freelist_alloc+32>: cmp %rbx,-0x8(%rax)
 PC (0x7ff076586410) ok
 source "%rbx" ok
 destination "-0x8(%rax)" (0x00000019) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 freelist_alloc (size=3, reuse=1) at /build/buildd/glib2.0-2.31.20/./gobject/gatomicarray.c:70
 _g_atomic_array_copy (array=<optimized out>, header_size=<optimized out>, additional_element_size=2) at /build/buildd/glib2.0-2.31.20/./gobject/gatomicarray.c:135
 iface_node_set_offset_L (iface_node=0x7ff07d3b30c0, offset=2, index=2) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1325
 type_node_add_iface_entry_W (node=0x7ff07d3e8580, iface_type=140670869909696, parent_entry=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1422
 type_add_interface_Wm (node=0x7ff07d3e8580, iface=0x7ff07d3b30c0, info=0x7fffb991b2a0, plugin=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1455
Title: chromium-browser crashed with SIGSEGV in freelist_alloc()
UpgradeStatus: Upgraded to precise on 2012-02-19 (26 days ago)
UserGroups: adm admin cdrom libvirtd lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 freelist_alloc (size=3, reuse=1) at /build/buildd/glib2.0-2.31.20/./gobject/gatomicarray.c:70
 _g_atomic_array_copy (array=<optimized out>, header_size=<optimized out>, additional_element_size=2) at /build/buildd/glib2.0-2.31.20/./gobject/gatomicarray.c:135
 iface_node_set_offset_L (iface_node=0x7ff07d3b30c0, offset=2, index=2) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1325
 type_node_add_iface_entry_W (node=0x7ff07d3e8580, iface_type=140670869909696, parent_entry=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1422
 type_add_interface_Wm (node=0x7ff07d3e8580, iface=0x7ff07d3b30c0, info=0x7fffb991b2a0, plugin=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:1455

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
C de-Avillez (hggdh2)
visibility: private → public
tags: added: qa-manual-testing
Revision history for this message
Olivier Tilloy (osomon) wrote :

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.

Changed in chromium-browser (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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