RESOLVED FIXED Bug 107432
[Soup] Use synchronous calls to close completely processed streams 
https://bugs.webkit.org/show_bug.cgi?id=107432
Summary [Soup] Use synchronous calls to close completely processed streams
Sergio Villar Senin
Reported 2013-01-21 02:01:04 PST
[Soup] Use synchronous calls to close completely processed streams
Attachments
Patch (4.74 KB, patch)
2013-01-21 02:10 PST, Sergio Villar Senin 		mrobinson: review+
svillar: commit-queue-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Sergio Villar Senin
Comment 1 2013-01-21 02:10:10 PST
Created attachment 183739 [details] Patch
Sergio Villar Senin
Comment 2 2013-01-21 05:09:10 PST
We might even think about removing the close() completely as streams are automatically closed once their last reference is dropped...
Martin Robinson
Comment 3 2013-01-21 08:09:32 PST
Comment on attachment 183739 [details] Patch Great! Might be good to get Dan to look at this one too.
Dan Winship
Comment 4 2013-01-21 08:10:33 PST
(In reply to comment #2) > We might even think about removing the close() completely as streams are automatically closed once their last reference is dropped... I wouldn't recommend that, because if something was holding a ref on the stream for a while for some reason after we were done reading, that would prevent the connection from being reused for another request.
Sergio Villar Senin
Comment 5 2013-01-21 08:27:48 PST
(In reply to comment #3) > (From update of attachment 183739 [details]) > Great! Might be good to get Dan to look at this one too. Cool, I'll wait until we have a clear idea about what triggers the crashes I'm seeing in bug 107439 tough.
Sergio Villar Senin
Comment 6 2013-01-21 08:28:26 PST
Comment on attachment 183739 [details] Patch Do not land this automatically, just in case.
Sergio Villar Senin
Comment 7 2013-02-19 07:17:52 PST
Committed r143329: <http://trac.webkit.org/changeset/143329>
Note You need to log in before you can comment on or make changes to this bug.