After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711842 - Soup blocks on internal socket close call
Soup blocks on internal socket close call
Status: RESOLVED DUPLICATE of bug 710494
Product: libsoup
Classification: Core
Component: Misc
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-11 12:59 UTC by Michael Wood
Modified: 2013-11-15 15:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use async version of g_io_stream_close to prevent blocking (976 bytes, patch)
2013-11-11 12:59 UTC, Michael Wood 		none Details | Review

Description Michael Wood 2013-11-11 12:59:19 UTC 
Created attachment 259557 [details] [review]
Use async version of g_io_stream_close to prevent blocking

In gnome-initial-setup we have a dialog box with the sign in page for adding a gnome-online-account service (such as flickr etc). On cancelling this before the page has fully loaded we get stuck in libsoup waiting for the socket to be closed.

(gnome-initial-setup:20446): goa-DEBUG: < HTTP/1.1 1 Cancelled
(gnome-initial-setup:20446): goa-DEBUG: < Soup-Debug-Timestamp: 1384173962
(gnome-initial-setup:20446): goa-DEBUG: < Soup-Debug: SoupMessage 0 (0x1654c70)
(gnome-initial-setup:20446): goa-DEBUG:  

see bug 711837
Comment 1 Dan Winship 2013-11-15 15:55:58 UTC 
fixed in master and 2.44.2

*** This bug has been marked as a duplicate of bug 710494 ***