epiphany-browser crashed with SIGSEGV in WTF::StringImpl::endsWith()

[Colan Schwartz]

Not sure what happened. Just found the crash window.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: epiphany-browser 3.10.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Oct 19 14:34:52 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/epiphany-browser
ProcCmdline: epiphany-browser
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fece362ab72 <_ZNK3WTF10StringImpl8endsWithEPKcjb+34>: cmp (%rdi),%ax
 PC (0x7fece362ab72) ok
 source "(%rdi)" (0x7fec0000ffd7) not located in a known VMA region (needed readable region)!
 destination "%ax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 WTF::StringImpl::endsWith(char const*, unsigned int, bool) const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-3.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-3.0.so.25
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-3.0.so.25
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-3.0.so.25
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-3.0.so.25
Title: epiphany-browser crashed with SIGSEGV in WTF::StringImpl::endsWith()
UpgradeStatus: Upgraded to trusty on 2014-05-20 (152 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare staff sudo whoopsie

[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 #1278777, 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.