chromium-browser crashed with SIGSEGV in gethostbyname2_r()

[Wojciech Myszka]

chromium crashed when relaunched after upgrade

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.65~r124586-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
ChromiumPrefs:
 browser/check_default_browser = **unset** (no such key yet)
 extensions/settings =
  - 'ahfgeienlihckogmohjhadlkjgocpleb'
      manifest/* = *undef*
Date: Mon Mar 5 19:45:33 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
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7faf7887abfe: lock xadd %eax,0x18(%rdi)
 PC (0x7faf7887abfe) 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_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 gethostbyname2_r () from /lib/x86_64-linux-gnu/libc.so.6
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=""

[Apport retracing service (apport)]

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.