| /external/valgrind/docs/html/ |
| quick-start.html | 132 <p>The stack trace tells you where the leaked memory was allocated.
133 Memcheck cannot tell you why the memory leaked, unfortunately.
|
| /external/valgrind/docs/internals/ |
| xml-output.txt | 271 bytes and blocks leaked by this error.
343 to them are also in leaked blocks
|
| /libcore/ojluni/src/main/java/java/util/concurrent/ |
| FutureTask.java | 281 // leaked interrupts
318 // leaked interrupts
|
| /system/bt/btif/src/ |
| btif_gatt_client.cc | 385 // clang-tidy analyzer complains about |params| is leaked. It doesn't know
408 // clang-tidy analyzer complains about |params| is leaked. It doesn't know
|
| /bionic/libc/malloc_debug/ |
| README.md | 247 then the log will include the backtrace of the leaked allocations. This
257 04-15 12:35:33.304 7412 7412 E malloc_debug: +++ APP leaked block of size 100 at 0x2be3b0b0 (leak 1 of 2)
263 04-15 12:35:33.305 7412 7412 E malloc_debug: +++ APP leaked block of size 24 at 0x7be32380 (leak 2 of 2)
582 you whether it can detect leaked memory, not where those leaks are
|
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/test/ |
| pystone.py | 20 First, it leaked memory: in Proc1(), NextRecord ends
|
| /external/clang/test/Modules/ |
| explicit-build-flags.cpp | 60 #error FOO leaked from module
|
| /external/google-breakpad/src/testing/src/ |
| gmock.cc | 41 "true iff Google Mock should report leaked mock objects "
|
| /external/googletest/googlemock/src/ |
| gmock.cc | 41 "true iff Google Mock should report leaked mock objects "
|
| /external/libchrome/base/message_loop/ |
| message_loop_task_runner_unittest.cc | 249 // The PostTaskAndReplyRelay is leaked here. Even if we had a reference to
|
| /external/libmicrohttpd/src/microhttpd/ |
| memorypool.c | 196 * allocation may be leaked until the pool is
|
| /external/libxml2/ |
| testOOM.c | 365 fprintf (stdout, "%d blocks leaked\n",
|
| /external/python/cpython2/Doc/c-api/ |
| list.rst | 122 leaked.
|
| /external/python/cpython2/Lib/test/ |
| pystone.py | 20 First, it leaked memory: in Proc1(), NextRecord ends
|
| /external/python/cpython3/Lib/test/libregrtest/ |
| refleak.py | 113 msg = '%s leaked %s %s, sum=%s' % (
|
| runtest.py | 142 refleak = False # True if the test leaked references.
|
| /external/python/cpython3/Lib/test/ |
| pystone.py | 20 First, it leaked memory: in Proc1(), NextRecord ends
|
| /external/toybox/ |
| main.c | 157 // Return if stack depth getting noticeable (proxy for leaked heap, etc).
|
| /external/v8/testing/gmock/src/ |
| gmock.cc | 41 "true iff Google Mock should report leaked mock objects "
|
| /external/valgrind/memcheck/ |
| mc_include.h | 387 IndirectLeak =2, // Leaked, but reachable from another leaked block
389 Unreached =3 // Not reached, ie. leaked.
440 /* A loss record, used for generating err msgs. Multiple leaked blocks can be
|
| /external/valgrind/memcheck/tests/ |
| leak-delta.stderr.exp | 66 leaked: 32 bytes in 1 blocks
|
| /external/vulkan-validation-layers/layers/ |
| README.md | 46 (build dir)/layers/object_tracker.cpp (name=`VK_LAYER_LUNARG_object_tracker`) - Track object creation, use, and destruction. As objects are created they are stored in a map. As objects are used the layer verifies they exist in the map, flagging errors for unknown objects. As objects are destroyed they are removed from the map. At `vkDestroyDevice()` and `vkDestroyInstance()` times, if any objects have not been destroyed they are reported as leaked objects. If a Dbg callback function is registered this layer will use callback function(s) for reporting, otherwise it will use stdout.
|
| /external/webrtc/talk/app/webrtc/ |
| dtlsidentitystore.cc | 203 // leaked even if the task does not get run.
|
| /external/webrtc/talk/app/webrtc/java/android/org/webrtc/ |
| GlRectDrawer.java | 221 * Release all GLES resources. This needs to be done manually, otherwise the resources are leaked.
|
| /external/wycheproof/ |
| README.md | 174 [CVE-2003-0971 - GnuPG generated ElGamal signatures that leaked the private key]
|
