Bug 37855

Summary: [Qt] cleaning up QNetworkReply
Product: WebKit Reporter: Johannes Zellner <johannes.zellner@nokia.com>
Component: WebKit QtAssignee: Nobody <webkit-unassigned@lists.webkit.org>
Status: RESOLVED INVALID    
Severity: Normal CC: adjam7@gmail.com, benjamin@webkit.org, markus@woboq.com, pd@webkit.dobrogost.net
Priority: P3 Keywords: EasyFix, Qt, QtTriaged
Version: 418.x   
Hardware: PC   
OS: Linux   

Description From 2010-04-20 06:59:26 PST
Regarding the documentation it is not quite clear who is when responsible to cleanup the QNetworkReply used in the signals QWebPage::unsupportedContent(QNetworkReply *reply); and QWebPage::finished(QNetworkReply*)

Using "deleteLater()" on the QNetworkReply, as stated in the docs, is ok in the SLOT connected to QWebPage::unsupportedContent(QNetworkReply *reply), but leads to segfault if used in the SLOT connected to QWebPage::finished(QNetworkReply*)
------- Comment #1 From 2010-05-12 08:08:35 PST -------
Can you please provide a simple test case for this?
------- Comment #2 From 2010-06-13 02:14:41 PST -------
There's no
QWebPage::finished(QNetworkReply*) [signal]
present in the API. There are
void QWebPage::loadFinished ( bool ok ) [signal]
and 
void QNetworkAccessManager::finished ( QNetworkReply * reply ) [signal]

Did you mean the second one?
------- Comment #3 From 2010-06-14 01:01:03 PST -------
sorry you are right, I meant the 

void QNetworkAccessManager::finished ( QNetworkReply * reply ) [signal]
------- Comment #4 From 2014-02-03 03:13:29 PST -------
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.