Searched
full:leak (Results
1451 -
1475 of
2655) sorted by null
<<51525354555657585960>>
/external/valgrind/memcheck/ |
mc_malloc_wrappers.c | 215 the mc->data field isn't visible to the leak checker. If memory 766 the mp->data field isn't visible to the leak checker. If memory [all...] |
/external/valgrind/memcheck/tests/amd64/ |
sh-mem-vec256-plo-no.stderr.exp | 938 For a detailed leak analysis, rerun with: --leak-check=full
|
/frameworks/base/core/java/android/widget/ |
AutoCompleteTextView.java | [all...] |
/frameworks/base/keystore/java/android/security/keystore/ |
KeyProtection.java | 389 * weaknesses due to which ciphertext may leak information about plaintext. For example, if a 719 * of weaknesses due to which ciphertext may leak information about plaintext. For example, [all...] |
/prebuilts/go/darwin-x86/src/os/exec/ |
exec_test.go | 546 // doesn't leak to the child, 553 // Make sure duplicated fds don't leak to the child.
|
/prebuilts/go/linux-x86/src/os/exec/ |
exec_test.go | 546 // doesn't leak to the child, 553 // Make sure duplicated fds don't leak to the child.
|
/prebuilts/misc/common/swig/include/2.0.11/python/ |
pyrun.swg | 537 printf("swig/python detected a memory leak of type '%s', no destructor found.\n", (name ? name : "unknown")); [all...] |
/external/freetype/docs/ |
CHANGES | [all...] |
/art/openjdkjvmti/ |
events-inl.h | 249 // future we might have jvmtiEnv's keep track of their allocations for leak-checking.
|
/art/runtime/jit/ |
jit.cc | 347 // When running sanitized, let all tasks finish to not leak. Otherwise just clear the queue.
|
/art/runtime/verifier/ |
reg_type_cache.cc | 342 // code cannot leak to other users.
|
/bionic/libc/bionic/ |
malloc_common.cpp | 338 // leak reports, close them here.
|
/bionic/libc/malloc_debug/ |
Config.cpp | 410 error_log(" Enable the leak tracking of memory allocations.");
|
PointerData.cpp | 441 error_log("+++ %s leaked block of size %zu at 0x%" PRIxPTR " (leak %zu of %zu)", getprogname(),
|
/bionic/libc/malloc_debug/tests/ |
malloc_debug_config_tests.cpp | 124 "6 malloc_debug Enable the leak tracking of memory allocations.\n" [all...] |
/development/host/windows/usb/adb_winapi_test/ |
adb_winapi_test.cpp | 729 // leak handles during the test.
|
/development/samples/Home/src/com/example/android/home/ |
Home.java | 161 // Remove the callback for the cached drawables or we leak
|
/device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.10/Modules/zlib/ |
ChangeLog | 314 - Fix memory leak on error in gz_open()
368 - Fix memory leaks in gzclose_r() and gzclose_w(), file leak in gz_open()
[all...] |
/device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/test/ |
test_gc.py | 622 gc.set_debug(debug & ~gc.DEBUG_LEAK) # this test is supposed to leak
|
test_memoryio.py | 355 # This will be caught by regrtest.py -R if this leak.
|
/device/linaro/bootloader/edk2/MdeModulePkg/Universal/Network/Ip4Dxe/ |
Ip4Driver.c | 1002 // that means there is a resource leak.
|
/device/linaro/bootloader/edk2/NetworkPkg/Ip6Dxe/ |
Ip6Driver.c | 988 // that means there is a resource leak.
|
/external/boringssl/src/crypto/cipher_extra/ |
aead_test.cc | 396 // Running a second, failed _init should not cause a memory leak.
|
tls_cbc.c | 346 // can't leak where. However, |num_starting_blocks| worth of data can
|
/external/boringssl/src/crypto/dsa/ |
dsa.c | 881 // We do not want timing information to leak the length of k,
|
Completed in 1262 milliseconds
<<51525354555657585960>>