Bug 154881 - [SOUP] Network process crash in WebKit::DownloadClient::didFinishLoading
Summary: [SOUP] Network process crash in WebKit::DownloadClient::didFinishLoading
Status: RESOLVED FIXED
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: 2016-03-01 15:20 PST by Michael Catanzaro
Modified: 2016-03-01 16:45 PST (History)
2 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 2016-03-01 15:20:38 PST 
Version-Release number of selected component:
webkitgtk4-2.10.3-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitNetworkProcess 14
crash_function: WebKit::DownloadClient::didFinishLoading
executable:     /usr/libexec/webkit2gtk-4.0/WebKitNetworkProcess
global_pid:     588
kernel:         4.2.5-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 WebKit::DownloadClient::didFinishLoading at /usr/src/debug/webkitgtk-2.10.3/Source/WebKit2/Shared/Downloads/soup/DownloadSoup.cpp:157
 #1 WebCore::readCallback at /usr/src/debug/webkitgtk-2.10.3/Source/WebCore/platform/network/soup/ResourceHandleSoup.cpp:1340
 #2 async_ready_callback_wrapper at ginputstream.c:529
 #3 g_task_return_now at gtask.c:1104
 #4 complete_in_idle_cb at gtask.c:1118
 #9 WTF::RunLoop::run at /usr/src/debug/webkitgtk-2.10.3/Source/WTF/wtf/glib/RunLoopGLib.cpp:67
 #10 WebKit::ChildProcessMain<WebKit::NetworkProcess, WebKit::NetworkProcessMain> at /usr/src/debug/webkitgtk-2.10.3/Source/WebKit2/Shared/unix/ChildProcessMain.h:61
 #12 _start

Full backtrace downstream.
Comment 1 Michael Catanzaro 2016-03-01 16:45:27 PST 
Yet another one the crash server thinks is fixed sorry again.

I am skeptical because we have only two reports of this, so no clue why the dumb crash server thinks no additional reports is any indication that it might be fixed, but two reports is officially too few for me to care about this one.