chromium-browser crashed with SIGSEGV in getaddrinfo()

[awol]

did not open a window - just crashed starting

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.83~r127885-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic-pae 3.2.12
Uname: Linux 3.2.0-19-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Mar 22 20:10:52 2012
Desktop-Session:
 DESKTOP_SESSION = xubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/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" - Beta i386 (20120301)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x285bc425: lock xadd %ecx,0xc(%eax)
 PC (0x285bc425) 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: Upgraded to precise on 2012-03-11 (11 days ago)
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 #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.