Bug 149565 - [SOUP] Crash in WebKit::CustomProtocolManagerImpl::didReceiveResponse
Summary: [SOUP] Crash in WebKit::CustomProtocolManagerImpl::didReceiveResponse
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-25 13:49 PDT by Michael Catanzaro
Modified: 2017-01-02 07:48 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2015-09-25 13:49:01 PDT 
Full backtrace downstream.

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 WebKit::CustomProtocolManagerImpl::didReceiveResponse at /usr/src/debug/webkitgtk-2.8.5/Source/WebKit2/Shared/Network/CustomProtocols/soup/CustomProtocolManagerImpl.cpp:176
 #1 callMemberFunctionImpl<WebKit::CustomProtocolManager, void (WebKit::CustomProtocolManager::*)(unsigned long, WebCore::ResourceResponse const&, unsigned int), std::tuple<unsigned long, WebCore::ResourceResponse, unsigned int>, 0ul, 1ul, 2ul> at /usr/src/debug/webkitgtk-2.8.5/Source/WebKit2/Platform/IPC/HandleMessage.h:16
 #2 callMemberFunction<WebKit::CustomProtocolManager, void (WebKit::CustomProtocolManager::*)(unsigned long, WebCore::ResourceResponse const&, unsigned int), std::tuple<unsigned long, WebCore::ResourceResponse, unsigned int>, std::make_index_sequence<3ul> > at /usr/src/debug/webkitgtk-2.8.5/Source/WebKit2/Platform/IPC/HandleMessage.h:22
 #3 IPC::handleMessage<Messages::CustomProtocolManager::DidReceiveResponse, WebKit::CustomProtocolManager, void (WebKit::CustomProtocolManager::*)(unsigned long, WebCore::ResourceResponse const&, unsigned int)> at /usr/src/debug/webkitgtk-2.8.5/Source/WebKit2/Platform/IPC/HandleMessage.h:92
 #4 WebKit::CustomProtocolManager::didReceiveMessage at /usr/src/debug/webkitgtk-2.8.5/x86_64-redhat-linux-gnu/DerivedSources/WebKit2/CustomProtocolManagerMessageReceiver.cpp:52
 #5 IPC::Connection::dispatchWorkQueueMessageReceiverMessage at /usr/src/debug/webkitgtk-2.8.5/Source/WebKit2/Platform/IPC/Connection.cpp:308
 #6 operator() at /usr/include/c++/5.1.1/functional:2271
 #7 WTF::GMainLoopSource::voidCallback at /usr/src/debug/webkitgtk-2.8.5/Source/WTF/wtf/gobject/GMainLoopSource.cpp:365
 #8 WTF::GMainLoopSource::voidSourceCallback at /usr/src/debug/webkitgtk-2.8.5/Source/WTF/wtf/gobject/GMainLoopSource.cpp:456
 #13 operator() at /usr/include/c++/5.1.1/functional:2271
Comment 1 Carlos Garcia Campos 2015-09-26 01:46:39 PDT 
This could be the one Mario promised he was going to fix :-P
Comment 2 Michael Catanzaro 2017-01-02 07:48:52 PST 
No reports of this in Fedora since 2.10.4, so closing this. But note that it is similar to bug #165082 and bug #165655.