Ubuntu
chromium-browser package

chromium-browser crashed with SIGSEGV

Bug #976568 reported by Mark Rooney on 2012-04-08

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	chromium-browser (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

Updated from 11.10 to 12.04 beta 2 and kept all settings in home folder, after update re-installed Chromium.

Started Chromium and it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 18.0.1025.142~r129054-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sun Apr 8 23:08:23 2012
Disassembly: => 0x7f20bf4309fe: Cannot access memory at address 0x7f20bf4309fe
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
?? ()
?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Tags:

Revision history for this message

Mark Rooney (rooney-mark-a) wrote on 2012-04-08:

#1

ChromiumPrefs.txt Edit (15.2 KiB, text/plain; charset="utf-8")
CoreDump.gz Edit (1.1 MiB, application/x-gzip)
Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Desktop-Session.txt Edit (153 bytes, text/plain; charset="utf-8")
DetectedPlugins.txt Edit (1.5 KiB, text/plain; charset="utf-8")
DiskUsage.txt Edit (616 bytes, text/plain; charset="utf-8")
InstalledPlugins.txt Edit (978 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (45.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (818 bytes, text/plain; charset="utf-8")
Registers.txt Edit (787 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (791 bytes, text/plain; charset="utf-8")
RelatedPackagesPolicy.txt Edit (2.7 KiB, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (224 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (127 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (9.4 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (537 bytes, text/plain; charset="utf-8")
gconf-keys.txt Edit (487 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-08:

#2

StacktraceTop:
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-08: Stacktrace.txt

#3

Stacktrace.txt Edit (127 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-08: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (10.1 KiB, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

Olivier Tilloy (osomon) wrote on 2017-04-25:

#5

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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