Ubuntu
chromium-browser package

chromium-browser crashed with SIGSEGV

Bug #969487 reported by Alvaro Leal (Effenberg0x0) on 2012-03-30

26

This bug affects 5 people

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

Bug Description

Updated: This bug only happens when right-clicking chromium-browser launcher-icon on Unity Launcher and selecting "Incognito Mode" from the quicklist. Launching the browser normally, with a left click on the launcher works fine as expected.

The error message is:
chromium-browse[24584]: segfault at 108 ip 00007ff8ce0469d5 sp 00007fffe2e90340 error 4 in chromium-browser[7ff8cd9f9000+3ca8000]

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.83~r127885-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu1
Architecture: amd64
Date: Fri Mar 30 15:32:20 2012
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120324.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --incognito
ProcEnviron:

SegvReason: reading NULL VMA
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=""

See original description

Tags:

Revision history for this message

Alvaro Leal (Effenberg0x0) (effenberg0x0) wrote on 2012-03-30:

#1

ChromiumPrefs.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
Desktop-Session.txt Edit (153 bytes, text/plain; charset="utf-8")
DetectedPlugins.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (561 bytes, text/plain; charset="utf-8")
DiskUsage.txt Edit (836 bytes, text/plain; charset="utf-8")
InstalledPlugins.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (57.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (820 bytes, text/plain; charset="utf-8")
Registers.txt Edit (733 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (760 bytes, text/plain; charset="utf-8")
RelatedPackagesPolicy.txt Edit (2.6 KiB, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (200 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (17.6 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (242.4 KiB, text/plain; charset="utf-8")
gconf-keys.txt Edit (486 bytes, text/plain; charset="utf-8")

description:

updated

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-30: Stacktrace.txt

#3

Stacktrace.txt Edit (1.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-30: StacktraceTop.txt

#4

StacktraceTop.txt Edit (651 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-30: ThreadStacktrace.txt

#5

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

Changed in chromium-browser (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Alvaro Leal (Effenberg0x0) (effenberg0x0) wrote on 2012-03-30:

#6

This bug was confirmed by other testers at UbuntuForums Ubuntu+1 sub-forum in this thread:
http://ubuntuforums.org/showthread.php?t=1949661

Changed in chromium-browser (Ubuntu):
status:	New → Confirmed
visibility:	private → public

Revision history for this message

Alvaro Leal (Effenberg0x0) (effenberg0x0) wrote on 2012-04-01:

#7

A working solution was posted at the following link (Comment #13):
http://code.google.com/p/chromium/issues/detail?id=113950

It turns out, users need to open Chromium-Browser in normal mode, and either:
-Login with Google/Gmail accounts at least once and close the browser.
- Click the "No, Thanks" button
- Close the browser.

At this point, launching it to "Incognito mode" via Quicklist - starts working.

Revision history for this message

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

#9

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

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

chromium #113950 Edit

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