WebResourceLoader is not always correct when second-guessing whether to send a response to DidReceiveResponseWithCertificateInfo.
Created attachment 199926 [details]
Comment on attachment 199926 [details]
Clearing flags on attachment: 199926
Committed r149251: <http://trac.webkit.org/changeset/149251>
All reviewed patches have been landed. Closing bug.
This re-introduced the crashed fixed in https://bugs.webkit.org/show_bug.cgi?id=115061
"...alrady canceled..." ? :)
Sadly, this means that the bug is much harder to fix - the null check being necessary means that we can't send messages back.
Re-added the null check in <http://trac.webkit.org/r149298>.
Created attachment 200126 [details]
This patch was originally written by Alexey, reviewed by me, then tweaked and tested heavily by me... so I'll give him a chance to review back!
Comment on attachment 200126 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=200126&action=review
> + // If m_coreLoader becomse null as a result of the didReceiveResponse callback, we can't use the send function().