epiphany-browser crashed with SIGSEGV in umemcasecmp()

[John Karp]

Binary package hint: epiphany-browser

Ubuntu 10.04.1 LTS

I had an ask.metafilter.com tab open, which I was just reading, I was not invoking any special commands when the crash occured.

This sort of crash seems to happen intermittantly, it usually happens after a couple hours of browsing pages. I haven't noticed any particular type of situation or type of page that triggers it.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: epiphany-browser 2.30.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 21 01:15:54 2010
ExecutablePath: /usr/bin/epiphany-browser
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: epiphany-browser
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/usr/bin/zsh
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 umemcasecmp (feature=..., version=...)
 WebCore::CaseFoldingHash::equal (feature=..., version=...)
 WebCore::CaseFoldingHash::equal (feature=..., version=...)
 WTF::IdentityHashTranslator<WebCore::String, WebCore::String, WebCore::CaseFoldingHash>::equal (feature=..., version=...)
 lookup<WebCore::String, WTF::IdentityHashTranslator<WebCore::String, WebCore::String, WebCore::CaseFoldingHash> > (feature=..., version=...)
Title: epiphany-browser crashed with SIGSEGV in umemcasecmp()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version. Thanks in advance and sorry for the late response.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!