chromium-browser crashed with SIGSEGV in tcmalloc::FL_Next()

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

Bug Description

powered down the computer while a number of apps were running including chromium

on powering the computer on and logging in, noticed the crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: chromium-browser 25.0.1364.160-0ubuntu3
Uname: Linux 3.9.0-030900rc6-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 9 12:17:43 2013
Desktop-Session:
 DESKTOP_SESSION = gnome
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2013-03-19 (21 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130319)
MarkForUpload: True
ProcCmdline: chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/mozilla/plugins/libflashplayer.so\ --lang=en-US\ --channel=13961.11.20690712
SegvAnalysis:
 Segfault happened at: 0x7f84d96c8dab: xor 0x8(%rbx),%rdx
 PC (0x7f84d96c8dab) ok
 source "0x8(%rbx)" (0xfffffffc03d934a1) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 calloc ()
 pa_xmalloc0 () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
Title: chromium-browser crashed with SIGSEGV in calloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %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'

Revision history for this message
Jeremiah Njoroge (jnjoroge) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tcmalloc::FL_Next(void*) ()
 tcmalloc::FL_Pop(void**) ()
 calloc ()
 ?? ()
 ?? ()

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
summary: - chromium-browser crashed with SIGSEGV in calloc()
+ chromium-browser crashed with SIGSEGV in tcmalloc::FL_Next()
tags: removed: need-amd64-retrace
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
assignee: nobody → Chad Miller (cmiller)
status: New → Confirmed
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: Confirmed → Won't Fix
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.

Other bug subscribers

Remote bug watches

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