| /build/kati/ |
| dep.cc | 551 // TODO: leak.
660 // TODO: This would be incorrect and has a leak.
|
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Modules/ |
| readline.c | 364 structure; this needs to be freed to avoid a memory leak. This version of
904 * XXX: A bug in the readline-2.2 library causes a memory leak
|
| /device/linaro/bootloader/edk2/BaseTools/Source/C/VfrCompile/Pccts/ |
| CHANGES_FROM_131.txt | 115 Memory leak is now gone from ANTLRTokenBuf; all tokens are deleted.
379 will "leak".
|
| /external/compiler-rt/lib/asan/ |
| asan_interceptors.cc | 271 // the |arg| pointer. This may cause LSan to report a leak if leak checking
|
| /external/deqp/external/vulkancts/framework/vulkan/ |
| vkAllocationCallbackUtil.cpp | 606 log << TestLog::Message << "LEAK " << (numLeaks+1) << ": " << record << TestLog::EndMessage;
623 log << TestLog::Message << "LEAK " << (numLeaks+1) << ": " << totalAllocated
|
| /external/google-breakpad/src/testing/src/ |
| gmock-spec-builders.cc | 523 bool leakable; // true iff it's OK to leak the object.
550 if (it->second.leakable) // The user said it's fine to leak this object.
|
| /external/icu/android_icu4j/src/main/java/android/icu/util/ |
| StringTrieBuilder.java | 149 // registered node, then get() failed to find that and we will leak newNode.
172 // registered node, then get() failed to find that and we will leak newNode.
[all...] |
| /external/icu/icu4c/source/common/ |
| stringtriebuilder.cpp | 334 // registered node, then uhash_find() failed to find that and we will leak newNode.
363 // registered node, then uhash_find() failed to find that and we will leak newNode.
|
| /external/icu/icu4j/main/classes/core/src/com/ibm/icu/util/ |
| StringTrieBuilder.java | 151 // registered node, then get() failed to find that and we will leak newNode.
174 // registered node, then get() failed to find that and we will leak newNode.
[all...] |
| /external/jemalloc/src/ |
| chunk.c | 555 * unlikely failure. Leak chunk after making sure its
557 * a virtual memory leak.
|
| /external/libchrome/base/process/ |
| launch_posix.cc | 161 // The motivation for going through all of them is that sa_restorer can leak
192 // Now ask the kernel again and check that no restorer will leak.
|
| /external/libchrome/crypto/ |
| nss_util.cc | 181 // NOTE(willchan): We don't actually execute this code since we leak NSS to
743 // NOTE(willchan): We don't actually execute this code since we leak NSS to
[all...] |
| /external/libxml2/ |
| ChangeLog | 171 * threads.c: patch from Daniel Zimmermann fixing a memory leak
460 * runsuite.c: small cleanup for non-leak reports
[all...] |
| /external/llvm/docs/CommandGuide/ |
| lit.rst | 124 .. option:: --vg-leak
126 When :option:`--vg` is used, enable memory leak checks. When this option is
|
| /external/python/cpython2/Modules/ |
| readline.c | 379 structure; this needs to be freed to avoid a memory leak. This version of
983 * XXX: A bug in the readline-2.2 library causes a memory leak
[all...] |
| /external/python/cpython3/Misc/ |
| HISTORY | 270 - Issue #25725: Fixed a reference leak in pickle.loads() when unpickling
276 - Issue #25688: Fixed file leak in ElementTree.iterparse() raising an error.
294 - Issue #25578: Fix (another) memory leak in SSLSocket.getpeercer().
313 - Issue #25569: Fix memory leak in SSLSocket.getpeercert().
[all...] |
| NEWS | 72 - Issue #29034: Fix memory leak and use-after-free in os module (path_converter).
137 - bpo-29110: Fix file object leak in aifc.open() when file is given as a
354 - Issue #28147: Fix a memory leak in split-table dictionaries: setattr()
578 - Issue #23782: Fixed possible memory leak in _PyTraceback_Add() and exception
834 - Issue #27778: Fix a memory leak in os.getrandom() when the getrandom() is
837 - Issue #28200: Fix memory leak on Windows in the os module (fix
843 - Issue #27932: Prevent memory leak in win32_ver().
[all...] |
| /external/v8/src/ |
| keys.cc | 275 // have to make sure to never directly leak the enum cache.
447 // Do not leak the enum cache as it might end up as an elements backing store.
[all...] |
| /external/valgrind/memcheck/tests/common/ |
| sh-mem-vec128-plo-yes.stderr.exp-32bit-le | 464 For a detailed leak analysis, rerun with: --leak-check=full
|
| sh-mem-vec128-plo-yes.stderr.exp-64bit-le | 464 For a detailed leak analysis, rerun with: --leak-check=full
|
| /toolchain/binutils/binutils-2.27/binutils/ |
| nlmheader.y | 830 /* FIXME: Possible memory leak. */
850 /* FIXME: Possible memory leak. */
|
| /external/curl/docs/ |
| INTERNALS.md | 510 that might give us problems if we "leak" them. The functions in the memdebug
747 Please note that this memory leak system is not adjusted to work in more
758 it will be easier if you actually do find a leak in the library.
789 If this doesn't produce any output, no leak was detected in libcurl. Then
790 the leak is mostly likely to be in your code.
[all...] |
| /external/clang/test/Analysis/ |
| retain-release-path-notes.m | 48 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
53 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
61 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
67 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
73 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
105 return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
115 return object; // expected-warning{{leak}} expected-note{{Object returned to caller as an owning reference (single retain count transferred to caller)}} expected-note{{Object leaked: object allocated and stored into 'object' is returned from a function whose name ('CFGetRuleViolation') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation}}
136 return result; // expected-warning{{leak}} expected-note{{Object returned to caller as an owning reference (single retain count transferred to caller)}} expected-note{{Object leaked: object allocated and stored into 'result' is returned from a method whose name ('getViolation') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa}}
226 id x = [[MyObj alloc] initX]; // expected-warning {{Potential leak of an object}}
237 id z = [[MyObj alloc] initZ]; // expected-warning {{Potential leak of an object}
[all...] |
| /prebuilts/clang/host/linux-x86/clang-3289846/lib64/clang/3.8/lib/linux/ |
| libclang_rt.asan-x86_64.a | [all...] |
| /prebuilts/clang/host/linux-x86/clang-3859424/lib64/clang/4.0/lib/linux/ |
| libclang_rt.asan-x86_64.a | [all...] |
