Description of problem: The tab crashes, showing the Oops! page, when going to this page and scrolling down: http://www.publico.pt/local/noticia/sindicato-anuncia-adiamento-de-greve-no-metro-de-lisboa-1687386 Version-Release number of selected component: webkitgtk4-2.6.5-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 60 crash_function: __strcmp_sse2_unaligned executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess kernel: 3.18.7-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29 #1 g_str_equal at ghash.c:1776 #2 ephy_web_dom_utils_find_form_auth_elements at ../../lib/ephy-web-dom-utils.c:401 #3 web_page_document_loaded at ephy-web-extension.c:959 #4 _g_closure_invoke_va at gclosure.c:831 #7 WebKit::InjectedBundlePageLoaderClient::didFinishDocumentLoadForFrame at /usr/src/debug/webkitgtk-2.6.5/Source/WebKit2/WebProcess/InjectedBundle/InjectedBundlePageLoaderClient.cpp:132 #8 WebKit::WebFrameLoaderClient::dispatchDidFinishDocumentLoad at /usr/src/debug/webkitgtk-2.6.5/Source/WebKit2/WebProcess/WebCoreSupport/WebFrameLoaderClient.cpp:516 #9 WebCore::FrameLoader::finishedParsing at /usr/src/debug/webkitgtk-2.6.5/Source/WebCore/loader/FrameLoader.cpp:763 #10 WebCore::Document::finishedParsing at /usr/src/debug/webkitgtk-2.6.5/Source/WebCore/dom/Document.cpp:4578 #11 WebCore::HTMLConstructionSite::finishedParsing at /usr/src/debug/webkitgtk-2.6.5/Source/WebCore/html/parser/HTMLConstructionSite.cpp:395
Created attachment 995828 [details] File: backtrace
Created attachment 995829 [details] File: cgroup
Created attachment 995830 [details] File: core_backtrace
Created attachment 995831 [details] File: dso_list
Created attachment 995832 [details] File: environ
Created attachment 995833 [details] File: exploitable
Created attachment 995834 [details] File: limits
Created attachment 995835 [details] File: maps
Created attachment 995836 [details] File: open_fds
Created attachment 995837 [details] File: proc_pid_status
Created attachment 995838 [details] File: var_log_messages
*** Bug 1197071 has been marked as a duplicate of this bug. ***
It's because "GObject DOM bindings API now correctly returns NULL intead of empty strings to be able to differentiate between not present and present but empty" in 2.6.5. We knew that was a risky change. Oh well.
epiphany-3.15.90-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/epiphany-3.15.90-3.fc22
Package epiphany-3.15.90-3.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing epiphany-3.15.90-3.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2873/epiphany-3.15.90-3.fc22 then log in and leave karma (feedback).
(In reply to Fedora Update System from comment #14) > epiphany-3.15.90-3.fc22 has been submitted as an update for Fedora 22. > https://admin.fedoraproject.org/updates/epiphany-3.15.90-3.fc22 But you reported this bug against Fedora 21. I will do an update for that too.
epiphany-3.14.2-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/epiphany-3.14.2-4.fc21
Package epiphany-3.14.2-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing epiphany-3.14.2-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2891/epiphany-3.14.2-4.fc21 then log in and leave karma (feedback).
Works fine now when go to www.deezer.com thnak you.
epiphany-3.14.2-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1192792 has been marked as a duplicate of this bug. ***