| /external/chromium_org/chrome/browser/ui/cocoa/location_bar/ |
| autocomplete_text_field_editor_unittest.mm | 185 // Test drawing, mostly to ensure nothing leaks or crashes.
191 // Test setting gray text, mostly to ensure nothing leaks or crashes.
|
| /external/chromium_org/third_party/libxml/src/ |
| check-relaxng-test-suite2.py | 96 # print "validating instance %d line %d leaks" % (
151 # print "validating instance %d line %d leaks %d bytes" % (
|
| check-xsddata-test-suite.py | 95 print "validating instance %d line %d leaks" % (
149 # print "validating instance %d line %d leaks" % (
|
| /external/clang/tools/scan-build/ |
| scan-build.1 | 257 Check for leaks and improper reference count management.
321 Check for memory leaks, double free, and use-after-free.
|
| /external/stlport/doc/ |
| FAQ | 46 Q6.2 My tool detects memory leaks in applications with STLport. Is this leak
470 Q6.2 My tool detects memory leaks in application with STLport. Is this leak
473 A6.2 In most cases these are 'pseudo memory leaks' that some tools
484 leaks, for memory that isn't freed when no longer used. These tools may report
485 false memory leaks when one uses STLport's node allocator. The memory chunk is
487 leaks before that point. Another memory problem might be reported when you use
496 There are ways to remove the pseudo memory leaks (since the memory is properly
497 freed at the end of the program, the leaks are just pseudo-ones). You could use
|
| /external/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /external/valgrind/main/docs/xml/ |
| quick-start-guide.xml | 77 memory errors and leaks that it detects.</para>
170 <para>There are several kinds of leaks; the two most important
|
| /ndk/sources/cxx-stl/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /prebuilts/ndk/5/sources/cxx-stl/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /prebuilts/ndk/6/sources/cxx-stl/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /prebuilts/ndk/7/sources/cxx-stl/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /prebuilts/ndk/8/sources/cxx-stl/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /prebuilts/ndk/9/sources/cxx-stl/EH/stlport/stlport/stl/config/ |
| host.h | 96 * memory chunks. Normally not required. But if you worry about quazi-leaks
97 * (may be reported by some leaks detection tools), use
|
| /external/valgrind/main/memcheck/docs/ |
| mc-manual.xml | 48 <para>Memory leaks.</para>
381 <sect2 id="mc-manual.leaks" xreflabel="Memory leak detection">
508 not necessarily the best way that leaks could be reported; in particular,
575 <para>Because there are different kinds of leaks with different severities, an
576 interesting question is this: which leaks should be counted as true "errors"
619 <para>When enabled, search for memory leaks when the client
621 many leaks occurred. If set to <varname>full</varname> or
644 be the same for the purposes of merging multiple leaks into a single
657 leaks. It only changes how the results are presented.</para>
[all...] |
| /art/runtime/ |
| jni_internal.h | 175 // TODO: to avoid leaks (and bugs), we need to clear this vector on entry (or return)
|
| /development/samples/training/threadsample/src/com/example/android/threadsample/ |
| PhotoFragment.java | 140 // If the View object still exists, delete references to avoid memory leaks
|
| /external/chromium/base/memory/ |
| linked_ptr.h | 11 // - Like all reference counting schemes, cycles lead to leaks.
|
| ref_counted.h | 172 // avoid common memory leaks caused by forgetting to Release an object
|
| /external/chromium/base/win/ |
| scoped_variant.h | 23 // against memory leaks.
|
| /external/chromium/chrome/browser/autofill/ |
| autofill_metrics.cc | 131 // Note that this leaks memory; that is expected behavior.
|
| /external/chromium/chrome/browser/ |
| background_contents_service_unittest.cc | 110 // Check for creation and leaks.
|
| browser_main_mac.mm | 120 // TODO(viettrungluu): crbug.com/20504 - This currently leaks, so if you
|
| /external/chromium/chrome/browser/search_engines/ |
| template_url_model_test_util.cc | 120 // before shutting down the I/O thread to avoid memory leaks.
|
| /external/chromium/chrome/browser/ui/cocoa/bookmarks/ |
| bookmark_button_unittest.mm | 66 // Make sure nothing leaks
|
| /external/chromium/chrome/browser/ui/cocoa/ |
| styled_text_field_unittest.mm | 115 // Test drawing, mostly to ensure nothing leaks or crashes.
|
