Updates:
Status: Available
Owner: ---
Cc: [email protected]
Comment #8 on issue 6531 by [email protected]: [MLK]
WebCore::ResourceHandle::ResourceHandle(ResourceRequest::WebCore
const&,ResourceHandleClient::WebCore *,bool,bool,bool) [CHROME.DLL]
http://code.google.com/p/chromium/issues/detail?id=6531
I think this is why we have leaks:
- The test downloads a gif file, the URL request goes to WebKit which
creates a ref
counted ResourceHandle. We increment reference to it in
ResourceHandleInternal and
will deref this only when we get ViewMsg_Resource_RequestComplete.
- Since its a file download it gets handled by
DownloadResourceHandler::OnResponseCompleted() which doesn't call the next
handler in
the chain (which would have led to
AsyncResourceHandler::OnResponseCompleted to send
RequestComplete IPC msg).
So after the load finishes the ResourceHandle object is still left with
reference
count of one. I dont think the hacky solution of deleting ResourceHandle in
MainResourceLoader destructor would fly with WebKit folks so we need a
better
solution.
Can we send ViewMsg_Resource_RequestComplete from
DownloadResourceHandler::OnResponseCompleted()?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
