Bug 86562 - DocumentLoader wastes vector capacity
Summary: DocumentLoader wastes vector capacity
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 86281
  Show dependency tree / graph
 
Reported: 2012-05-15 20:20 PDT by Simon Fraser (smfr)
Modified: 2014-05-16 09:18 PDT (History)
5 users (show)

See Also:

Attachments
A patch from mother issue modified for latest version (23.36 KB, patch)
2014-03-10 08:44 PDT, Wojciech Bielawski 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2012-05-15 20:20:10 PDT 
9 vectors, 2.27KB used of 32.62KB, 30.36KB wasted at:
1   0x108e022c4 WebCore::DocumentLoader::DocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&)
2   0x108395263 WebKit::WebFrameLoaderClient::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&)
3   0x108f7d367 WebCore::FrameLoader::loadWithNavigationAction(WebCore::ResourceRequest const&, WebCore::NavigationAction const&, bool, WebCore::FrameLoadType, WTF::PassRefPtr<WebCore::FormState>)
4   0x108f7b450 WebCore::FrameLoader::loadURL(WebCore::KURL const&, WTF::String const&, WTF::String const&, bool, WebCore::FrameLoadType, WTF::PassRefPtr<WebCore::Event>, WTF::PassRefPtr<WebCore::FormState>)
5   0x108f7a1dd WebCore::FrameLoader::loadURLIntoChildFrame(WebCore::KURL const&, WTF::String const&, WebCore::Frame*)
Comment 1 Wojciech Bielawski 2014-03-10 02:56:03 PDT 
Looks like it's not a Loader problem any more. I've tested latest vesion of webkit and there was no Loader related classes on the lists.
Comment 2 Wojciech Bielawski 2014-03-10 08:44:56 PDT 
Created attachment 226305 [details]
A patch from mother issue modified for latest version

EFL port was tested with attached patch
Comment 3 Wojciech Bielawski 2014-05-16 01:08:20 PDT 
Simon would you mind closing it as a resolved/works for me? According to EFL port this issue is not relevant.