chromium-browser crashed with SIGSEGV in __nscd_get_mapping()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed on startup.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 16.0.912.
ProcVersionSign
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: 2f383a1679e8525
CheckboxSystem: bb422ca46d02494
CrashCounter: 1
Date: Sun Feb 12 15:29:15 2012
Desktop-Session:
DESKTOP_SESSION = ubuntu
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
DuplicateOf: https:/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
ProcCmdline: /usr/lib/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f168745dc2e <__nscd_
PC (0x7f168745dc2e) 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:
__nscd_get_mapping (type=<optimized out>, key=0x7f16874abbb0 "hosts", mappedp=
__nscd_get_map_ref (type=GETFDHST, name=<optimized out>, mapptr=
nscd_gethst_r (key=0x7f169153a738 "ssl.gstatic.com", keylen=16, type=GETHOSTBYNAME, resultbuf=
__nscd_
__gethostbyname2_r (name=0x7f16915
Title: chromium-browser crashed with SIGSEGV in __nscd_
UpgradeStatus: Upgraded to precise on 2012-01-12 (30 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""
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.