Memory leak caught in WebCore/platform/network/qt/QNetworkReplyHandler.cpp. Function QNetworkReply::abort()
Created attachment 40790 [details] patch
Comment on attachment 40790 [details] patch Wow. deleteLater() is a very scary memory management model. But OK I trust you. rubber-stamp=me.
(In reply to comment #2) > (From update of attachment 40790 [details]) > Wow. deleteLater() is a very scary memory management model. But OK I trust > you. rubber-stamp=me. Eric, Please set this to r- as it may cause problem. I am working on that. Sorry.
Created attachment 41662 [details] 2nd patch
What sort of problems did the other patch cause? Can we test those problems with a unit test/layout test?
(In reply to comment #5) > What sort of problems did the other patch cause? Can we test those problems > with a unit test/layout test? If m_reply is NOT unhooked from QNetworkReplyHandler in release() function, it may reference QNetworkReplyHandler after the latter is deleted. This is the problem of the first patch. Not sure how to come up with a test case... It's related to download.
Comment on attachment 41662 [details] 2nd patch Ideally your ChangeLog would give explanations like this, and make some small statement about why this change is untestable.
Created attachment 41670 [details] update ChangeLog
Comment on attachment 41670 [details] update ChangeLog OK. I'm not a Qt expert, but as far as I can tell this looks sane.
Comment on attachment 41670 [details] update ChangeLog Clearing flags on attachment: 41670 Committed r49951: <http://trac.webkit.org/changeset/49951>
All reviewed patches have been landed. Closing bug.