chromium-browser crashed with SIGSEGV

Bug #1295116 reported by Karma Dorje
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

 in the browser address bar i just typed the letter of the Russian alphabet — «ч»

apt-cache policy chromium-browser
chromium-browser:
  Installed: 32.0.1700.107-0ubuntu1~20140204.977.1
  Candidate: 32.0.1700.107-0ubuntu1~20140204.977.1
  Version table:
 *** 32.0.1700.107-0ubuntu1~20140204.977.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 32.0.1700.107-0ubuntu1~20140204.977.1
Uname: Linux 3.14.0-031400rc5-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Mar 20 20:43:01 2014
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/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 2012-09-30 (536 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1)
ProcCmdline: chromium-browser\ --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ --ppapi-flash-version=12.0.0.70
SegvAnalysis:
 Segfault happened at: 0x7f9a8987557d: mov 0x10(%rax),%rdx
 PC (0x7f9a8987557d) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2013-11-10 (129 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
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'
mtime.conffile..etc.chromium.browser.default: 2014-02-24T07:07:20.065993

Revision history for this message
Karma Dorje (taaroa) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1286902, 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.

tags: removed: need-amd64-retrace
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.