Project: v8 Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 601 Memory leak from V8, detected on Chromium Linux Valgrind bot
Starred by 5 users Project Member Reported by pkasting@chromium.org, Feb 8 2010 Back to list
Status: Fixed
Owner:
User never visited
Closed: Jul 2014
Cc:
HW: ----
OS: Linux
Priority: ----
Type: Bug



Sign in to add a comment
I first saw this leak in 
http://build.chromium.org/buildbot/memory/builders/Webkit%20Linux%20(valgri
nd%20layout)/builds/5633/steps/valgrind%20test:%20layout/logs/stdio , there 
are a number of runs after that with similar failures.

Here is a set of suppressions that covers what I've seen so far:

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:malloc
   fun:_ZN3WTF10fastMallocEj
   fun:_ZN3WTF13FastAllocBasenwEj
   fun:_ZN7WebCore17DOMImplementation6createEv
   fun:_ZNK7WebCore8Document14implementationEv
   
fun:_ZN7WebCore10V8Document28implementationAccessorGetterEN2v85LocalINS1_6S
tringEEERKNS1_12AccessorInfoE
   
fun:_ZN2v88internal6Object23GetPropertyWithCallbackEPS1_S2_PNS0_6StringES2_
   obj:*
}

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:malloc
   fun:_ZN3WTF10fastMallocEj
   fun:_ZN3WTF13FastAllocBasenwEj
   fun:_ZN7WebCore17DOMImplementation6createEv
   fun:_ZNK7WebCore8Document14implementationEv
   fun:_ZN7WebCore8Document13setXMLVersionERKNS_6StringERi
   fun:_ZN7WebCore12XMLTokenizer13startDocumentEPKhS2_i
   fun:_ZN7WebCore20startDocumentHandlerEPv
   fun:xmlParseTryOrFinish
   fun:xmlParseChunk
   fun:_ZN7WebCore12XMLTokenizer7doWriteERKNS_6StringE
   fun:_ZN7WebCore12XMLTokenizer5writeERKNS_15SegmentedStringEb
   fun:_ZN7WebCore8Document5writeERKNS_15SegmentedStringEPS0_
   fun:_ZN7WebCore8Document5writeERKNS_6StringEPS0_
   fun:_ZN7WebCore9DOMParser15parseFromStringERKNS_6StringES3_
   
fun:_ZN7WebCore17DOMParserInternal23parseFromStringCallbackERKN2v89Argument
sE
   
fun:_ZN2v88internal19HandleApiCallHelperILb0EEEPNS0_6ObjectENS0_99_GLOBAL__
N__b_slave_webkit_rel_linux_valgrind_layout_build_src_v8_src_builtins.cc_00
000000_7C6A375416BuiltinArgumentsILNS0_21BuiltinExtraArgumentsE1EEE
}

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:malloc
   fun:_ZN3WTF10fastMallocEj
   fun:_ZN3WTF13FastAllocBasenwEj
   ...
   
fun:_ZN7WebCore10HTMLParser11handleErrorEPNS_4NodeEbRKNS_12AtomicStringEi
   fun:_ZN7WebCore10HTMLParser10insertNodeEPNS_4NodeEb
   
fun:_ZN7WebCore10HTMLParser11handleErrorEPNS_4NodeEbRKNS_12AtomicStringEi
   fun:_ZN7WebCore10HTMLParser10insertNodeEPNS_4NodeEb
   fun:_ZN7WebCore10HTMLParser30insertNodeAfterLimitBlockDepthEPNS_4NodeEb
   fun:_ZN7WebCore10HTMLParser10parseTokenEPNS_5TokenE
   fun:_ZN7WebCore13HTMLTokenizer12processTokenEv
   fun:_ZN7WebCore13HTMLTokenizer5writeERKNS_15SegmentedStringEb
   fun:_ZN7WebCore8Document5writeERKNS_15SegmentedStringEPS0_
   fun:_ZN7WebCore8Document5writeERKNS_6StringEPS0_
   fun:_ZN7WebCore14V8HTMLDocument13writeCallbackERKN2v89ArgumentsE
   
fun:_ZN2v88internal19HandleApiCallHelperILb0EEEPNS0_6ObjectENS0_99_GLOBAL__
N__b_slave_webkit_rel_linux_valgrind_layout_build_src_v8_src_builtins.cc_00
000000_7C6A375416BuiltinArgumentsILNS0_21BuiltinExtraArgumentsE1EEE
}

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:malloc
   fun:_ZN3WTF10fastMallocEj
   fun:_ZN3WTF13FastAllocBasenwEj
   ...
   
fun:_ZN2v88internal8JSObject26GetPropertyWithInterceptorEPS1_PNS0_6StringEP
18PropertyAttributes
   obj:*
}

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:malloc
   fun:_ZN3WTF10fastMallocEj
   fun:_ZN3WTF13FastAllocBasenwEj
   fun:_ZN7WebCore11WebKitPoint6createEff
   fun:_ZN7WebCore13V8WebKitPoint19constructorCallbackERKN2v89ArgumentsE
   
fun:_ZN2v88internal19HandleApiCallHelperILb1EEEPNS0_6ObjectENS0_99_GLOBAL__
N__b_slave_webkit_rel_linux_valgrind_layout_build_src_v8_src_builtins.cc_00
000000_7C6A375416BuiltinArgumentsILNS0_21BuiltinExtraArgumentsE1EEE
   obj:*
}
 
Labels: Type-Bug OS-Linux
Looks like a duplicate of http://code.google.com/p/chromium/issues/detail?id=34994
The root cause sounds the same.  On that bug glider suppressed Heapcheck:Leak issues, 
whereas I was looking at Memcheck:Leak problems; it's a bit harder to suppress those 
with a small set of suppressions (see the stacks above).  I'll note this bug on that 
one.
Status: Fixed
Long outdated, though some suppressions are still in place. There was an attempt to remove them, but that got reverted: https://codereview.chromium.org/111443009
Sign in to add a comment