RESOLVED INVALID 19808
LEAK: leak from WebCore::ImageSource::isSizeAvailable()
https://bugs.webkit.org/show_bug.cgi?id=19808
Summary LEAK: leak from WebCore::ImageSource::isSizeAvailable()
Cameron Zwarich (cpst)
Reported Sunday, June 29, 2008 6:27:59 AM UTC
I found this by running the stress test with MallocStackLogging enabled: Leak: 0x1a367600 size=3072 string 'Photoshop ICC profile' Call stack: [thread 0xa05a0fa0]: | 0xba4d6 | NSApplicationMain | -[NSApplication run] | 0x86be | -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] | _DPSNextEvent | BlockUntilNextEventMatchingListInMode | ReceiveNextEventCommon | RunCurrentEventLoopInMode | CFRunLoopRunInMode | CFRunLoopRunSpecific | muxerSourcePerform | _CFURLConnectionSendCallbacks | sendDidReceiveDataCallback | _NSURLConnectionDidReceiveData | -[NSURLConnection(NSURLConnectionReallyInternal) sendDidReceiveData:originalLength:] | -[WebCoreResourceHandleAsDelegate connection:didReceiveData:lengthReceived:] | WebCore::ResourceLoader::didReceiveData(WebCore::ResourceHandle*, char const*, int, int) | WebCore::SubresourceLoader::didReceiveData(char const*, int, long long, bool) | WebCore::Loader::Host::didReceiveData(WebCore::SubresourceLoader*, char const*, int) | WebCore::CachedImage::data(WTF::PassRefPtr<WebCore::SharedBuffer>, bool) | WebCore::Image::setData(WTF::PassRefPtr<WebCore::SharedBuffer>, bool) | WebCore::BitmapImage::dataChanged(bool) | WebCore::BitmapImage::isSizeAvailable() | WebCore::ImageSource::isSizeAvailable() | CGImageSourceCopyPropertiesAtIndex | CGImageSourceGetPropertiesAtIndex | makeImagePlus | _CGImagePluginInitPNG | _cg_png_read_info | png_handle_iCCP | png_malloc | malloc | malloc_zone_malloc
Attachments
Mark Rowe (bdash)
Comment 1 Sunday, June 29, 2008 6:31:54 AM UTC
This leak looks like it is inside ImageIO's color management rather than in WebKit itself.
Mark Rowe (bdash)
Comment 2 Sunday, June 29, 2008 7:07:40 AM UTC
Mark Rowe (bdash)
Comment 3 Sunday, June 29, 2008 7:09:55 AM UTC
Moved to Radar and sent to ImageIO.
Note You need to log in before you can comment on or make changes to this bug.