It's another bug that has appeared in WebKitSoupRequestInputStream after moving the custom protocols handling to the main thread. The problem is that webkitSoupRequestInputStreamPendingReadAsyncComplete invalidates pendingAsyncRead after calling webkitSoupRequestInputStreamReadAsyncResultComplete, but in some cases webkitSoupRequestInputStreamReadAsyncResultComplete completes the task in the same run loop iteration. In that case webkitSoupRequestInputStreamReadAsync is called again creating a new AsyncReadData that is destroyed right after webkitSoupRequestInputStreamReadAsyncResultComplete returns.
Created attachment 300731 [details]
Could this be the cause of bug #167887?
(In reply to comment #2)
> Could this be the cause of bug #167887?
I don't think so. I haven't looked at the yelp issue yet, but I would bet it's the same volume check.
Committed r211773: <http://trac.webkit.org/changeset/211773>