Lines Matching full:leak
4276 a slight memory leak, and it causes problems during JSGlobalData teardown.
7101 Fix a leak in Yarr.
9719 <rdar://problem/6692138> REGRESSION (Safari 4): Incorrect function return value when using IE "try ... finally" memory leak work-around (24654)
12430 Function argument names leak
16779 <rdar://problem/6445089> Mach ports leak from worker threads
19705 memory leak (failure to deallocate trampolines).
23634 Create DEFINE_STATIC_LOCAL macro. Change static local objects to leak to avoid
23909 misleading leak messages. There is still a lone JSC::Node leaking when
25301 (WTF::mainThreadFunctionQueueMutex): Changed to leak an object
25316 (WTF::threadMapMutex): Changed to leak an object rather than using
25320 (WTF::threadMap): Changed to leak an object rather than using
25695 - fix storage leak seen on buildbot
25697 Some other cleanup too. The storage leak was caused by the fact
25728 to have its default value: true, not false. This fixes the leak!
27087 * JavascriptCore.exp: Export leak-related functions..
28780 - fix for: REGRESSION: over 100 StructureIDs leak loading about:blank (result of fix for bug 21633)
29274 - Add leak ignore set to StructureID to selectively ignore leaking some StructureIDs.
29400 be cached twice. This leads to a memory leak in almost every use of
34150 LEAK messages appear every time I quit
34160 log the reason there was no leak checking done.
39560 a pointer, but it was not destructed, causing a huge leak in run-webkit-tests --threaded.
39782 hold JSStringRefs. This is necessary to avoid having to construct (and leak) a new instance
