chromium-browser crashed with SIGSEGV in gethostbyname2_r()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
In gnome-shell, trying to launch chromium just after login.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.
ProcVersionSign
Uname: Linux 3.2.0-18-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Wed Mar 14 08:12:26 2012
Desktop-Session:
DESKTOP_SESSION = gnome-classic
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/
ProcCwd: /home/juan
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0xb29e1005: lock xadd %ecx,0xc(%eax)
PC (0xb29e1005) ok
source "%ecx" ok
destination "0xc(%eax)" (0x0000000b) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
?? () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
gethostbyname2_r () from /lib/i386-
Title: chromium-browser crashed with SIGSEGV in gethostbyname2_r()
UpgradeStatus: Upgraded to precise on 2012-03-08 (6 days ago)
UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare vboxusers
chromium-default: CHROMIUM_FLAGS=""
| Juan Salamanca (juan-m-salamanca) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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 #929219, 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.