| /external/chromium_org/v8/tools/ |
| run-valgrind.py | 40 '--leak-check=full',
57 # Look through the leak details and make sure that we don't
70 # Make sure we found between 2 and 3 leak lines.
|
| /external/clang/test/Analysis/ |
| NewDelete-intersections.mm | 45 // expected-warning@-2 {{Potential leak of memory pointed to by 'p'}}
53 // expected-warning@-2 {{Potential leak of memory pointed to by 'p'}}
60 // expected-warning@-2 {{Potential leak of memory pointed to by 'p'}}
|
| properties.m | 46 NSString *string1 = [[NSString alloc] initWithFormat:@"test %f", 0.0]; // expected-warning {{Potential leak}}
133 p.name = [[NSString string] retain]; // expected-warning {{leak}}
134 p.name = [[NSString alloc] init]; // expected-warning {{leak}}
|
| /external/eigen/test/ |
| exceptions.cpp | 12 // - no memory leak when a custom scalar type trow an exceptions
83 VERIFY(ScalarWithExceptions::instances==before && "memory leak detected in " && EIGEN_MAKESTRING(OP)); \
103 VERIFY(ScalarWithExceptions::instances==0 && "global memory leak detected in " && EIGEN_MAKESTRING(OP)); \
|
| /external/v8/tools/ |
| run-valgrind.py | 40 '--leak-check=full',
57 # Look through the leak details and make sure that we don't
70 # Make sure we found between 2 and 3 leak lines.
|
| /external/valgrind/main/memcheck/tests/ |
| pointer-trace.c | 2 Make sure that leak-check's pointer tracing avoids traps, i.e. tricky
27 the below traps, and so checks that the leak checker
84 // We deliberately make a leak, it'll be obvious if something went
|
| partial_load_dflt.stderr.exp | 31 For a detailed leak analysis, rerun with: --leak-check=full
|
| partial_load_dflt.stderr.exp64 | 31 For a detailed leak analysis, rerun with: --leak-check=full
|
| partial_load_dflt.stderr.expr-s390x-mvc | 31 For a detailed leak analysis, rerun with: --leak-check=full
|
| /external/chromium/chrome/browser/ui/cocoa/bookmarks/ |
| bookmark_bar_folder_window.mm | 81 // window. However that also allows some scrollWheel: events to leak
83 // Better to plug the scroll leak than to round corners for M5.
|
| /external/chromium_org/chrome/browser/ui/cocoa/bookmarks/ |
| bookmark_bar_folder_window.mm | 80 // window. However that also allows some scrollWheel: events to leak
82 // Better to plug the scroll leak than to round corners for M5.
|
| /external/chromium_org/third_party/WebKit/Source/testing/plugin/Tests/ |
| LeakWindowScriptableObject.cpp | 59 // Leak both references to the window script object.
64 static PluginTest::Register<LeakWindowScriptableObject> leakWindowScriptableObject("leak-window-scriptable-object");
|
| /external/chromium_org/third_party/WebKit/Source/wtf/ |
| RefCountedLeakCounter.cpp | 75 LOG(RefCountedLeaks, "LEAK: %u %s", m_count, m_description);
78 LOG(RefCountedLeaks, "No leak checking done: %s", leakMessageSuppressionReasons->begin()->key);
|
| /external/chromium_org/third_party/zlib/contrib/minizip/ |
| ChangeLogUnzip | 3 - Fix possible memory leak in unzip.c (Zoran Stevanovic)
31 - fix memory leak in minizip.c
|
| /external/chromium_org/tools/heapcheck/ |
| heapcheck_test.py | 21 'Leak of ([0-9]*) bytes in ([0-9]*) objects allocated from:')
70 Analyze() searches the logs for leak reports and tries to apply
89 # leak signature: [number of bytes, number of objects]
107 # Try to find the suppression that applies to the current leak stack.
116 print 'Missing leak signature for the following stack: '
139 print ('Leak of %d bytes in %d objects allocated from:'
148 print ' Heapcheck:Leak'
242 'using-the-heap-leak-checker')
|
| /external/compiler-rt/lib/sanitizer_common/ |
| sanitizer_flags.h | 42 // Enable memory leak detection.
44 // Invoke leak checking in an atexit handler. Has no effect if
|
| /external/valgrind/main/memcheck/ |
| memcheck.h | 185 /* Do a full memory leak check (like --leak-check=full) mid-execution. */
192 since the previous leak search. */
198 increased or decreased leaked bytes/blocks since previous leak
204 /* Do a summary memory leak check (like --leak-check=summary) mid-execution. */
210 all previous leak checks. They must be lvalues. */
232 all previous leak checks. They must be lvalues. */
|
| /external/valgrind/main/memcheck/tests/linux/ |
| timerfd-syscall.stderr.exp | 53 For a detailed leak analysis, rerun with: --leak-check=full
|
| /external/chromium_org/third_party/tcmalloc/chromium/src/gperftools/ |
| heap-checker.h | 39 // no slowdown caused by this unless you activate the leak-checker:
48 // a memory leak at program-exit, it will print instructions on how
49 // to track down the leak.
81 // Static functions for working with (whole-program) leak checking.
83 // If heap leak checking is currently active in some mode
84 // e.g. if leak checking was started (and is still active now)
87 // constructed right now will be doing leak checking or nothing.
101 // Do whole-program leak check now (if it was activated for this binary);
111 // This requires that some leak check (e.g. NoGlobalLeaks())
116 // Non-static functions for starting and doing leak checking
[all...] |
| /external/chromium_org/third_party/tcmalloc/vendor/src/gperftools/ |
| heap-checker.h | 39 // no slowdown caused by this unless you activate the leak-checker:
48 // a memory leak at program-exit, it will print instructions on how
49 // to track down the leak.
81 // Static functions for working with (whole-program) leak checking.
83 // If heap leak checking is currently active in some mode
84 // e.g. if leak checking was started (and is still active now)
87 // constructed right now will be doing leak checking or nothing.
101 // Do whole-program leak check now (if it was activated for this binary);
111 // This requires that some leak check (e.g. NoGlobalLeaks())
116 // Non-static functions for starting and doing leak checking
[all...] |
| /external/chromium_org/third_party/tcmalloc/chromium/src/tests/ |
| heap-checker_unittest.cc | 39 // To test that the whole-program heap checker will actually cause a leak, try:
46 // otherwise the test can sometimes fail for tricky leak checks
56 // The implication of this for real leak checking
125 "If should cause a leak crash");
128 "If should cause a looped leak crash");
131 "If should cause a leak crash by hiding a pointer "
144 "to interfere with leak checking");
351 // This way we prevent leak checker from finding any temporary pointers
394 // of the same size as what we are going to leak to ensure that the object
395 // we are about to leak is not at the same address as some old allocate
[all...] |
| /external/chromium_org/third_party/tcmalloc/vendor/src/tests/ |
| heap-checker_unittest.cc | 39 // To test that the whole-program heap checker will actually cause a leak, try:
46 // otherwise the test can sometimes fail for tricky leak checks
56 // The implication of this for real leak checking
125 "If should cause a leak crash");
128 "If should cause a looped leak crash");
131 "If should cause a leak crash by hiding a pointer "
144 "to interfere with leak checking");
351 // This way we prevent leak checker from finding any temporary pointers
394 // of the same size as what we are going to leak to ensure that the object
395 // we are about to leak is not at the same address as some old allocate
[all...] |
| /cts/tests/tests/os/src/android/os/cts/ |
| IParcelFileDescriptorPeer.aidl | 45 void leak();
|
| /development/ndk/platforms/android-9/include/android/ |
| native_window_jni.h | 32 * when done with it so that it doesn't leak.
|
| /external/chromium/base/win/ |
| scoped_bstr.cc | 42 DCHECK(!bstr_) << "BSTR leak.";
|
