/external/mesa3d/docs/ |
relnotes-7.5.1.html | 57 <li>Fixed minor GLX memory leaks.
|
/external/nist-sip/java/gov/nist/javax/sip/ |
SipListenerExt.java | 44 * the dialog to avoid any dialog leaks.
|
/external/regex-re2/re2/ |
prefilter.h | 97 // Used for debugging, helps in tracking memory leaks.
|
/external/skia/src/core/ |
SkTypefaceCache.h | 63 * cache (e.g. to look for leaks).
|
/frameworks/base/media/mca/filterfw/native/core/ |
time_util.cpp | 74 // TODO: this leaks the NamedStopWatch objects. Replace it with a
|
/frameworks/base/media/mca/filterpacks/native/base/ |
time_util.cpp | 72 // TODO: this leaks the NamedStopWatch objects. Replace it with a
|
/frameworks/base/test-runner/src/android/test/ |
ActivityTestCase.java | 53 * to scrub out any class variables. This protects against memory leaks in the case where a
|
/external/chromium_org/content/browser/ |
browser_main_runner.cc | 130 // Invoke leak detection now, to avoid dealing with shutdown-only leaks. 134 // If leaks are found, the process will exit here.
|
/external/chromium_org/net/websockets/ |
websocket_inflater_test.cc | 169 // This is a test for detecting memory leaks with valgrind. 181 // This is a test for detecting memory leaks with valgrind.
|
/external/chromium_org/third_party/protobuf/src/google/protobuf/testing/ |
googletest.cc | 242 // Force shutdown at process exit so that we can test for memory leaks. To 243 // actually check for leaks, I suggest using the heap checker included with
|
/external/chromium_org/third_party/sqlite/src/ |
Makefile.arm-wince-mingw32ce-gcc | 56 # to check for memory leaks. Use SQLITE_DEBUG=2 to print a log of all 57 # malloc()s and free()s in order to track down memory leaks.
|
Makefile.linux-gcc | 50 # to check for memory leaks. Use SQLITE_DEBUG=2 to print a log of all 51 # malloc()s and free()s in order to track down memory leaks.
|
/external/protobuf/src/google/protobuf/testing/ |
googletest.cc | 241 // Force shutdown at process exit so that we can test for memory leaks. To 242 // actually check for leaks, I suggest using the heap checker included with
|
/frameworks/base/docs/html/training/load-data-background/ |
handle-results.jd | 116 in order to prevent memory leaks. Once 133 * This prevents memory leaks.
|
/frameworks/base/docs/html/tools/debugging/ |
debugging-memory.jd | 14 <li><a href="#TriggerLeaks">Triggering Memory Leaks</a></li> 316 window, so this can help you identify memory leaks involving dialogs or other windows. 324 are a good way to track large memory leaks.</dd> 391 <p>When analyzing your heap, you should look for memory leaks caused by:</p> 414 should be only a certain number. For example, a common source of leaks is additional instance of 473 <h2 id="TriggerLeaks">Triggering Memory Leaks</h2> 476 forcing memory leaks. One way to provoke memory leaks in your app is to let it 477 run for a while before inspecting the heap. Leaks will trickle up to the top of the allocations in
|
/development/samples/training/threadsample/src/com/example/android/threadsample/ |
PhotoView.java | 48 * reference prevents memory leaks and crashes, because it automatically tracks the "state" of 52 * Using a hard reference may cause memory leaks as the value continues to change; even worse, 175 * to prevent memory leaks.
|
/external/chromium_org/ppapi/tests/ |
test_instance_deprecated.cc | 224 // Leak some, but tell TestCase to ignore the leaks. This test is run and then 226 // run is torn down, they will show up as leaks in the second run. 241 // don't run the destructor for objects which the plugin leaks. This is to
|
/external/chromium_org/third_party/icu/source/test/intltest/ |
intltest.h | 111 virtual UBool setLeaks( UBool leaks = TRUE ); 225 UBool leaks; member in class:IntlTest 262 UBool run_phase2( char* name, char* par ); // internally, supports reporting memory leaks
|
/external/chromium_org/third_party/tcmalloc/chromium/src/tests/ |
heap-checker_unittest.cc | 120 // (i.e. we do detect leaks) 149 "so that it's hard to force leaks when threads are around"); 234 // If we can reliably create leaks (i.e. make leaked object 411 // "we detected a leak", and how to diagnose it, for *unexpected* leaks. 437 "Expected leaks not found: " 620 // test that we detect leaks when we have same total # of bytes and 687 // have different disabled leaks 693 // have different disabled leaks inside of a thread 704 // different disabled leaks (some in threads) 778 "Expected leaks not found: [all...] |
/external/chromium_org/third_party/tcmalloc/vendor/src/tests/ |
heap-checker_unittest.cc | 120 // (i.e. we do detect leaks) 149 "so that it's hard to force leaks when threads are around"); 234 // If we can reliably create leaks (i.e. make leaked object 411 // "we detected a leak", and how to diagnose it, for *unexpected* leaks. 437 "Expected leaks not found: " 620 // test that we detect leaks when we have same total # of bytes and 687 // have different disabled leaks 693 // have different disabled leaks inside of a thread 704 // different disabled leaks (some in threads) 778 "Expected leaks not found: [all...] |
/external/icu4c/test/intltest/ |
intltest.h | 137 virtual UBool setLeaks( UBool leaks = TRUE ); 273 UBool leaks; member in class:IntlTest 316 UBool run_phase2( char* name, char* par ); // internally, supports reporting memory leaks
|
/frameworks/av/libvideoeditor/vss/src/ |
M4xVSS_API.c | [all...] |
/cts/tests/tests/security/src/android/security/cts/ |
KernelSettingsTest.java | 108 * Compiling the config file into the kernel leaks the kernel base address
|
/external/chromium/chrome/browser/hang_monitor/ |
hung_plugin_action.cc | 82 // TODO: this leaks.
|
hung_window_detector.cc | 104 // TODO: this leaks.
|