Bug 12146 – REGRESSION: Memory leak in WebCore::Loader::servePendingRequests

• Status: RESOLVED
• Resolution: INVALID
• Component: Page Loading

[Mark Rowe (bdash)]

Buildbot is reporting a memory leak.  It's not clear which test is resulting in this.  Leaks output is as follows:

Process 926: 63949 nodes malloced for 18960 KB
Process 926: 1 leak for 1024 total leaked bytes.
Leak: 0x08952a00  size=1024	
	0x01873fd0 0x00000000 0x00000001 0x00000000 	..?.............
	0x00000000 0x00000000 0x00000000 0x00000000 	................
	0x08952a24 0x00000000 0xffffffff 0x00000000 	..*$............
	0xffffffff 0x00000000 0x00000028 0x00000027 	...........(...'
	0x00000001 0x00000004 0x00000007 0x00000007 	................
	0x00000007 0x00000007 0x00000007 0x00000096 	................
	0x00000096 0x00000096 0x00000000 0x404e0000 	............@N..
	0x00000000 0x00000000 0x00000000 0x00000000 	................
	...
	Call stack: [thread 6]: | 0x0 | start | _start | main | dumpRenderTree | runTest | -[NSRunLoop runMode:beforeDate:] | CFRunLoopRunSpecific | __CFRunLoopRun | __CFRunLoopDoSources0 | _sendCallbacks | -[NSURLConnection(NSURLConnectionInternal) _sendCallbacks] | -[NSURLConnection(NSURLConnectionInternal) _sendDidReceiveDataCallback] | -[WebCoreResourceHandleAsDelegate connection:didReceiveData:lengthReceived:] | WebCore::ResourceLoader::didReceiveData(WebCore::ResourceHandle*, char const*, int, int) | WebCore::MainResourceLoader::didReceiveData(char const*, int, long long, bool) | WebCore::ResourceLoader::didReceiveData(char const*, int, long long, bool) | WebCore::MainResourceLoader::addData(char const*, int, bool) | WebCore::FrameLoader::receivedData(char const*, int) | WebCore::DocumentLoader::receivedData(char const*, int) | WebCore::DocumentLoader::commitLoad(char const*, int) | WebCore::FrameLoader::committedLoad(WebCore::DocumentLoader*, char const*, int) | WebFrameLoaderClient::committedLoad(WebCore::DocumentLoader*, char const*, int) | -[WebDataSource(WebInternal) _receivedData:] | -[WebHTMLRepresentation receivedData:withDataSource:] | -[WebCoreFrameBridge receivedData:textEncodingName:] | -[WebCoreFrameBridge addData:] | WebCore::FrameLoader::addData(char const*, int) | WebCore::FrameLoader::write(char const*, int) | WebCore::XMLTokenizer::write(WebCore::SegmentedString const&, bool) | xmlParseChunk | xmlParseDocument | xmlParseStartTag | WebCore::endElementNsHandler(void*, unsigned char const*, unsigned char const*, unsigned char const*) | WebCore::XMLTokenizer::endElementNs() | WebCore::DocLoader::requestScript(WebCore::String const&, WebCore::String const&) | WebCore::DocLoader::requestResource(WebCore::CachedResource::Type, WebCore::String const&, WebCore::String const*) | WebCore::Cache::requestResource(WebCore::DocLoader*, WebCore::CachedResource::Type, WebCore::KURL const&, long, WebCore::String const*) | WebCore::createResource(WebCore::CachedResource::Type, WebCore::DocLoader*, WebCore::KURL const&, long, WebCore::String const*) | WebCore::CachedScript::CachedScript[in-charge](WebCore::DocLoader*, WebCore::String const&, WebCore::CachePolicy, long, WebCore::String const&) | WebCore::Loader::load(WebCore::DocLoader*, WebCore::CachedResource*, bool) | WebCore::Loader::servePendingRequests() | WebCore::SubresourceLoader::create(WebCore::Frame*, WebCore::SubresourceLoaderClient*, WebCore::ResourceRequest const&) | operator new(unsigned long) | WTF::fastMalloc(unsigned long)

[Mark Rowe (bdash)]

Brady suggested that one of Anders' recent changes may have introduced this leak.

[Darin Adler]

I think this single leak is a false positive, a bug in the leaks tool. It's very surprising that we see exactly one leak.

[Maciej Stachowiak]

<rdar://problem/4960658>

[Maciej Stachowiak]

<rdar://problem/4960502>

[Maciej Stachowiak]

Appears to be a bug in the 'leaks' tool per the Radar.