chromium-browser crashed with SIGSEGV in gethostbyname2_r()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Crashes using the HUD launcher
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.
ProcVersionSign
Uname: Linux 3.3.0-1-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 7 05:44:20 2012
Desktop-Session:
DESKTOP_SESSION = ubuntu-2d
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
EcryptfsInUse: Yes
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111209.1)
ProcCmdline: /usr/lib/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f45f8c60bfe: lock xadd %eax,0x18(%rdi)
PC (0x7f45f8c60bfe) ok
source "%eax" ok
destination "0x18(%rdi)" (0x00000017) 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/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
gethostbyname2_r () from /lib/x86_
Title: chromium-browser crashed with SIGSEGV in gethostbyname2_r()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
| Tim Gardner (timg-tpi) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-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.