chromium-browser crashed with SIGSEGV in __nscd_get_mapping()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is *probably* a dupe of lp:931082, lp:929219, and lp:929494 *at least*. This seems to be impacting a lot of users, given the number of dupes out there. Will wait for the retrace to set it to an actual duplicate.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.
ProcVersionSign
Uname: Linux 3.2.0-16-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Feb 16 10:15:34 2012
Desktop-Session:
DESKTOP_SESSION = ubuntu
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.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
ProcCmdline: /usr/lib/
ProcCwd: /home/john
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0xb29bc005 <__nscd_
PC (0xb29bc005) 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:
__nscd_get_mapping (type=GETFDHST, key=0xb29fa1b5 "hosts", mappedp=0xb2a40ac4) at nscd_helper.c:417
__nscd_
__check_pf (seen_ipv4=
__GI_getaddrinfo (name=0xb84d2fcc "mail.google.com", service=<optimized out>, hints=<optimized out>, pai=0xac14afc8) at ../sysdeps/
net::SystemHos
Title: chromium-browser crashed with SIGSEGV in __nscd_
UpgradeStatus: Upgraded to precise on 2011-12-02 (75 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare video
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 #931082, 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.