| /bionic/libc/bionic/ |
| malloc_debug_common.cpp | 31 * routines that are used by malloc leak detection code and other components in
35 * more tricky, malloc leak detection code, implemented in
39 * to all, leak detection code and other components via dynamic (libc.so),
266 * 1 - For memory leak detections.
450 InitMalloc(malloc_impl_handle, &gMallocUse, "leak");
|
| malloc_debug_check.cpp | 452 // just get a whole new allocation and leak the old one
525 log_message("+++ %s did not leak", exe);
534 log_message("+++ %s leaked block of size %d at %p (leak %d of %d)",
|
| /external/chromium_org/third_party/skia/src/animator/ |
| SkAnimator.cpp | 662 for (SkDisplayable** leak = SkDisplayable::fAllocations.begin(); leak < SkDisplayable::fAllocations.end(); leak++)
663 SkDebugf("%08x %s\n", *leak, (*leak)->id);
|
| /external/chromium_org/third_party/tcmalloc/chromium/src/ |
| heap-profile-table.h | 223 // used for leak checking (using HeapLeakChecker).
249 // Access to the allocation liveness flag (for leak checking)
255 // Should this allocation be ignored if it looks like a leak?
477 // Report anything in this snapshot as a leak.
516 // Helpers for sorting and generating leak reports
|
| /external/clang/test/Analysis/ |
| retain-release-inline.m | 283 NSString *s = [[NSString alloc] init]; // expected-warning {{Potential leak}}
304 return CFStringCreateWithCStringNoCopy(0, bytes, NSNEXTSTEPStringEncoding, 0); // expected-warning {{leak}}
313 id x = test_return_retained_NS(); // expected-warning {{leak}}
339 CFStringRef str = CFStringCreateWithCStringNoCopy(0, bytes, NSNEXTSTEPStringEncoding, 0); // expected-warning {{leak}}
387 return [[NSString alloc] init]; // expected-warning {{leak}}
|
| /external/skia/src/animator/ |
| SkAnimator.cpp | 662 for (SkDisplayable** leak = SkDisplayable::fAllocations.begin(); leak < SkDisplayable::fAllocations.end(); leak++)
663 SkDebugf("%08x %s\n", *leak, (*leak)->id);
|
| /external/clang/lib/StaticAnalyzer/Checkers/ |
| RetainCountChecker.cpp | 168 ErrorLeak, // A memory leak due to excessive reference counts.
169 ErrorLeakReturned, // A memory leak due to the returning method not having
[all...] |
| /external/chromium/chrome/browser/profiles/ |
| profile.cc | 264 // because we don't want to leak the sites that the user has visited before.
707 // We don't want SSLHostState from the OTR profile to leak back to the main
712 // Use a separate FindBarState so search terms do not leak back to the main
|
| /external/chromium_org/base/memory/ |
| scoped_ptr_unittest.cc | 401 // Test uncaught Pass() does not leak.
413 // Test that passing to function which does nothing does not leak.
440 // Test uncaught return type not leak.
|
| /external/clang/test/Driver/ |
| sanitizer-ld.c | 158 // RUN: -target x86_64-unknown-linux -fsanitize=leak \
168 // RUN: %clang -fsanitize=leak,undefined %s -### -o %t.o 2>&1 \
181 // RUN: %clang -fsanitize=leak,address %s -### -o %t.o 2>&1 \
|
| /frameworks/base/core/java/android/view/ |
| WindowManagerGlobal.java | 323 WindowLeaked leak = new WindowLeaked( local
326 leak.setStackTrace(root.getLocation().getStackTrace());
327 Log.e(TAG, "", leak);
|
| /frameworks/base/docs/html/tools/debugging/ |
| debugging-memory.jd | 35 development (which you should), you still might leak objects or introduce other memory bugs. The
102 continues to increase and doesn't ever seem to get smaller, you could have a memory leak.</p>
432 new tab that traces the references to that object which is causing the alleged leak.</p>
478 the heap. However, the smaller the leak, the longer you need to run the app in order to see it.</p>
480 <p>You can also trigger a memory leak in one of the following ways:</p>
483 activity states. Rotating the device can often cause an app to leak an {@link android.app.Activity},
|
| /external/chromium/sdch/open-vcdiff/src/ |
| rolling_hash.h | 100 // threads at the same time can only cause a memory leak, not incorrect
193 // (causing a memory leak), but the results will be consistent
|
| /external/chromium_org/base/process/ |
| launch.h | 70 // leak to the child process, causing errors such as open socket hangs.
146 // responsible for closing the handle so that it doesn't leak!
|
| /external/chromium_org/chrome/browser/chromeos/input_method/ |
| candidate_window_view_unittest.cc | 270 // We should call CloseNow method, otherwise this test will leak memory.
388 // We should call CloseNow method, otherwise this test will leak memory.
|
| /external/chromium_org/ppapi/tests/ |
| test_case.cc | 123 // leak.
210 // TODO(dmichael): Fix tests that leak resources and enable the following:
|
| /external/chromium_org/printing/backend/ |
| print_backend_cups.cc | 85 // GnuTLS has a genuine small memory leak that is easier to annotate
87 // TODO(earthdok): remove this once the leak is fixed.
|
| /external/chromium_org/sandbox/win/src/ |
| sharedmem_ipc_server.cc | 33 // Better to leak than to crash.
115 // abandoned. Note: We purposely leak the local handle because we want it to
|
| /external/chromium_org/sdch/open-vcdiff/src/ |
| rolling_hash.h | 101 // threads at the same time can only cause a memory leak, not incorrect
189 // (causing a memory leak), but the results will be consistent
|
| /external/chromium_org/third_party/tcmalloc/vendor/ |
| ChangeLog | 65 * Make PageHeap dynamically allocated for leak checks (maxim)
108 * Allow ignoring one object twice in the leak checker (glider)
285 * PORTING: Fix a leak when building with LLVM
313 * BUGFIX: disable hooks better when forking in leak-checker (csilvers)
330 * Rewrite leak-checking code: should be faster and more robust (sanjay)
433 * Improve thread-safety of leak checker (maxim)
510 * New documentation about how to handle common heap leak situations
597 cause error leak reports now (etune)
[all...] |
| /external/expat/ |
| Changes | 4 #2895533: CVE-2012-1147 - Resource leak in readfilemap.c.
14 #2958794: CVE-2012-1148 - Memory leak in poolGrow.
|
| /external/open-vcdiff/src/ |
| rolling_hash.h | 101 // threads at the same time can only cause a memory leak, not incorrect
189 // (causing a memory leak), but the results will be consistent
|
| /external/srec/portable/include/ |
| phashtable.h | 146 * deleting the table to avoid memory leak.
202 * function might cause a leak in the event that the key needs to be deleted.
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| stopping.jd | 84 you use {@link android.app.Activity#onStop()} to release resources that might leak memory.</p>
190 last chance to clean out resources that could lead to a memory leak, so you should be sure that
|
| /ndk/sources/host-tools/make-3.81/tests/ |
| run_make_tests.pl | 31 $valgrind_args = '--num-callers=15 --tool=memcheck --leak-check=full';
333 # -q --leak-check=yes
|
