| /external/clang/lib/StaticAnalyzer/Checkers/ |
| PointerArithChecker.cpp | 80 // TODO: intentional leak. Some information is garbage collected too early,
|
| StackAddrEscapeChecker.cpp | 10 // This file defines stack address leak checker, which checks if an invalid
|
| /external/clang/tools/scan-view/share/ |
| Reporter.py | 165 if bugtype.find("leak") != -1:
|
| /external/compiler-rt/lib/asan/ |
| asan_fake_stack.cc | 137 // as the result may leak one or more fake frames, but the good news is that
|
| /external/compiler-rt/lib/safestack/ |
| safestack.cc | 48 // leakage of the stack pointer can be prevented. Currently, libc can leak the
|
| /external/expat/doc/ |
| xmlwf.1 | 139 not a leak in \fBxmlwf\fR.
|
| /external/guava/guava/src/com/google/common/base/ |
| FinalizableReferenceQueue.java | 242 // This is used by the ClassLoader-leak test in FinalizableReferenceQueueTest to disable
|
| /external/guava/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/ |
| ImmutableSortedSet.java | 193 // a subset of another, to avoid memory leak.
|
| /external/honggfuzz/ |
| README.md | 40 * [Memory leak in __mod\_auth\_digest__ ? CVE-2017-9788](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9788)
|
| /external/icu/icu4c/source/common/ |
| uniset_closure.cpp | 42 // memory leak checker tools
|
| /external/iproute2/tc/ |
| m_xt_old.c | 155 /* On error paths, make sure that we don't leak memory */
|
| /external/libchrome/base/metrics/ |
| persistent_sample_map.cc | 251 // sample will not be persistent, will not be shared, and will leak...
|
| /external/libchrome/base/process/ |
| process_posix.cc | 315 // processes may take some time doing leak checking.
|
| /external/libcxx/docs/DesignDocs/ |
| VisibilityMacros.rst | 136 either hidden (via this macro) or inline, so that they don't leak into client
|
| /external/libcxx/include/ |
| thread | 192 // thread local data. For this reason we leak the key.
|
| /external/libedit/src/ |
| eln.c | 210 // XXX: The two strdup's leak
|
| /external/libevent/ |
| whatsnew-2.1.txt | 92 memory-leak-checking tools, because Libevent allocated some global
95 globally held resources before exiting, so that your leak-check tools
99 your process exit()s. If you aren't using a leak-checking tool, there
126 The event_base_once() function used to leak some memory if the event
[all...] |
| /external/libjpeg-turbo/ |
| jcapimin.c | 289 * memory leak if an app calls write_tables repeatedly without doing a full
|
| /external/libmojo/base/android/ |
| jni_android.cc | 152 // We intentionally leak the global ref since we now storing it as a raw
|
| /external/libmojo/mojo/edk/system/ |
| channel.h | 239 // Causes the platform handle to leak when this channel is shut down instead
|
| /external/libxml2/ |
| check-relaxng-test-suite.py | 393 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
|
| check-relaxng-test-suite2.py | 417 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
|
| check-xsddata-test-suite.py | 419 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
|
| /external/libxml2/test/namespaces/reconcile/ |
| tests-to-c.xsl | 211 printf("## '%s' MEMORY leak: %d\n", "</xsl:text>
|
| /external/linux-kselftest/tools/testing/selftests/x86/ |
| test_syscall_vdso.c | 168 printf("[OK]\tR8..R15 did not leak kernel data\n");
|
