Status: Untriaged
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-Linux Area-Misc Size-Medium valgrind

New issue 9499 by [email protected]: Leak in WebCore::getNamedItems in  
LayoutTests/http/tests/misc/acid3.html
http://code.google.com/p/chromium/issues/detail?id=9499

Saw this on an optimized build running the
LayoutTests/http/tests/misc/acid3.html layout test under valgrind:
(see also bug 9488 for a different problem under that test):

84 (20 direct, 64 indirect) bytes in 1 blocks are definitely lost in loss  
record 463 of 729
   operator new(unsigned int)  
(algrind/coregrind/m_replacemalloc/vg_replace_malloc.c:195)
   WebCore::getNamedItems(WebCore::HTMLCollection*, WebCore::String)
(/home/dank/chromium/src/chrome/Hammer/test_shell)
    
WebCore::V8Custom::v8HTMLCollectionNamedPropertyGetter(v8::Local<v8::String>,
v8::AccessorInfo const&) (/home/dank/chromium/src/chrome/Hammer/test_shell)
    
v8::internal::JSObject::GetPropertyWithInterceptor(v8::internal::JSObject*,
v8::internal::String*, PropertyAttributes*)
(/home/dank/chromium/src/chrome/Hammer/test_shell)

23:15:45 valgrind_analyze.py [ERROR] Leak_DefinitelyLost
72 bytes in 6 blocks are definitely lost in loss record 455 of 729
   operator new(unsigned int)  
(algrind/coregrind/m_replacemalloc/vg_replace_malloc.c:195)
   WebCore::V8Proxy::ToNativeNodeFilter(v8::Handle<v8::Value>)
(src/chrome/Hammer/test_shell)
   WebCore::DocumentInternal::createNodeIteratorCallback(v8::Arguments  
const&)
(src/chrome/Hammer/test_shell)
   v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**)
(src/chrome/Hammer/test_shell)


--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to