Bug 26922

Summary:

[Qt] Valgrind shows leaks in network layer

Product:

WebKit

Reporter:

Balazs Kelemen <kbalazs>

Component:

Platform

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED DUPLICATE

Severity:

Normal

CC:

hausmann, kling

Priority:

Keywords:

Version:

528+ (Nightly build)

Hardware:

OS:

Linux

Attachments:

Description	Flags
backtrace1	none
backtrace2	none

Balazs Kelemen

Reported 2009-07-02 05:10:06 PDT

For 2-3 months, valgrind shows me a leak linked with the network layer of the qt port. I could not find the error, but the code seems tricky enough to worry about it. The backtraces all contains ResourceHandle::create and ResourceHandle::start.

Attachments
backtrace1 (2.98 KB, text/plain) 2009-07-02 05:11 PDT, Balazs Kelemen	no flags	Details
backtrace2 (4.49 KB, text/plain) 2009-07-02 05:12 PDT, Balazs Kelemen	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Balazs Kelemen

Comment 1 2009-07-02 05:11:16 PDT

Created attachment 32178 [details] backtrace1

Balazs Kelemen

Comment 2 2009-07-02 05:12:26 PDT

Created attachment 32179 [details] backtrace2

Simon Hausmann

Comment 3 2009-07-02 05:22:09 PDT

It looks like the QNetworkReplyHandler isn't deleted. If you look at the ResourceHandle destructor you can see that it will end up calling QNetworkReplyHandler::abort() (indirectly), which in turn will issue a deleteLater() on the QNetworkReply as well as the QNetworkReplyHandler, which will delete it. Does the ResourceHandle destructor get called for you?

Balazs Kelemen

Comment 4 2009-07-02 05:56:34 PDT

Yes, it gets called a lot of times on every page loading. I am not sure about that the problem is the QNetworkReplyHandler.

Andreas Kling

Comment 5 2010-03-16 04:15:47 PDT

Unable to reproduce with ToT.

Balazs Kelemen

Comment 6 2010-03-16 06:06:08 PDT

I think this is a duplicate of 25023 what we have solved.

Balazs Kelemen

Comment 7 2010-03-16 06:06:41 PDT

*** This bug has been marked as a duplicate of bug 25023 ***

Note You need to log in before you can comment on or make changes to this bug.