chromium-browser crashed with SIGSEGV in __nscd_get_mapping()

Bug #931082 reported by Nabyl Baccar
620
This bug affects 147 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Crashed spontaneously..

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 16.0.912.77~r118311-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5
Uname: Linux 3.2.0-15-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 12 19:35:11 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/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
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120211)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+filebug/4a10eb92-55a8-11e1-9a5c-68b5996a96c8?field.title=unity-applications-daemon+crashed+with+SIGSEGV+in+dee_model_remove%28%29
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb2b88005: lock xadd %ecx,0xc(%eax)
 PC (0xb2b88005) 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-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 getaddrinfo () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: chromium-browser crashed with SIGSEGV in getaddrinfo()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Nabyl Baccar (nabylov) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __nscd_get_mapping (type=GETFDHST, key=0xb2bc61b5 "hosts", mappedp=0xb2c0cac4) at nscd_helper.c:417
 __nscd_get_nl_timestamp () at nscd_gethst_r.c:113
 __check_pf (seen_ipv4=0xad2a3f6e, seen_ipv6=0xad2a3f6f, in6ai=0xad2a3f58, in6ailen=0xad2a3f5c) at ../sysdeps/unix/sysv/linux/check_pf.c:322
 __GI_getaddrinfo (name=0xb8c3b12c "themes.googleusercontent.com", service=<optimized out>, hints=<optimized out>, pai=0xad2a3fd8) at ../sysdeps/posix/getaddrinfo.c:2372
 net::SystemHostResolverProc(std::string const&, net::AddressFamily, int, net::AddressList*, int*) ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
summary: - chromium-browser crashed with SIGSEGV in getaddrinfo()
+ chromium-browser crashed with SIGSEGV in __nscd_get_mapping()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Changed in chromium-browser (Ubuntu):
importance: Medium → High
tags: added: qa-manual-testing
Revision history for this message
Jayson Gundy (gundybears) wrote :

Occurs on 17.0.963.56 (Developer Build 121963 Linux) as well.

Revision history for this message
noname2 (noname2-deactivatedaccount) wrote :
no longer affects: chromium-browser
Revision history for this message
schiemanski (schiemanski) wrote :

Today chromium-browser crashed again. Sometimes it occurs when I want to start chromium up for the first time after boot. Then when i start it up for the second time, it will start up normally. (Xubuntu 12.04 Beta 1)

Revision history for this message
Hanine HAMZIOUI (hanynowsky) wrote :

Exactly same symptom as @schiemasnski (Ubuntu 12.05 Beta 1 Updated)

Revision history for this message
bquenin (bquenin) wrote :

same symptoms, first start crashes, subsequent starts are ok

Revision history for this message
Hasse Bylov (hassebylov) wrote :

A guess could be, that Chromium crashes sometimes, when there is no internet connection. Can anyone else confirm this?

Revision history for this message
Paulo Calvo (pcalvo56) wrote :

I got this error *with* an internet connection.

Revision history for this message
Aurélien RIVIERE (aurelien-riv) wrote :

Idem, but maybe it was a missing internet connexion on another port than HTTP/HTTPS ? My ufw deny ingoing and outgoing connexions except for :

ubuntu@precise:~$ sudo ufw status verbose
Status: active
Logging: off
Default: deny (incoming), deny (outgoing)
New profiles: skip

To Action From
-- ------ ----
80/tcp ALLOW IN Anywhere

80/tcp ALLOW OUT Anywhere
21/tcp ALLOW OUT Anywhere
53 ALLOW OUT Anywhere
5222/tcp ALLOW OUT Anywhere
443/tcp ALLOW OUT Anywhere

Revision history for this message
userdce (userdce) wrote :

I too got with internet connection

Revision history for this message
omarly666 (omarly666) wrote :

latest updates installed - reboot and crash on first attempt to launch chromium. second try works fine

Revision history for this message
nick3499-ubuntu-amd64 (nick3499) wrote :

I created a launcher in alacarte to launch Amazon Cloud Reader through synapse

chromium-browser https://read.amazon.com

chromium-browser typically loads read.amazon.com without a problem

Revision history for this message
nick3499-ubuntu-amd64 (nick3499) wrote :

this crash occurred after doing a
'dist-upgrade' in terminal,
then a 'reboot' from terminal.

after my system rebooted, I tried to launch 'chromium-browser',
but instead of launching, I received an error msg

Revision history for this message
Anatol Pomozov (anatol) wrote :

It somewhat similar to comment #17. I had a chromium browser crash when I tried to launch it during "apt dist-upgrade".

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.