| /tools/tradefederation/core/src/com/android/tradefed/targetprep/ |
| NativeLeakCollector.java | 41 @OptionClass(alias = "native-leak-collector")
|
| /external/mesa3d/docs/ |
| versions.html | 273 <li>fixed a memory leak in the context destroy function
440 <li>fixed a memory leak in glTexImage[12]D()
445 <li>fixed a memory leak in GLX code
487 <li>fixed potential image memory leak (wasn't setting reference counter)
494 <li>fixed memory leak in polygon tesselator (Randy Frank)
503 <li>fixed memory leak in glTexSubImage[123]D
[all...] |
| /external/scapy/scapy/layers/ |
| inet.py | [all...] |
| /frameworks/base/core/java/android/app/ |
| LoadedApk.java | 1147 IntentReceiverLeaked leak = new IntentReceiverLeaked( local
1175 ServiceConnectionLeaked leak = new ServiceConnectionLeaked( local
[all...] |
| /art/build/ |
| Android.gtest.mk | 477 --leak-check=full --error-exitcode=1 --workaround-gcc296-bugs=yes \
537 # Note: envsetup currently exports ASAN_OPTIONS=detect_leaks=0 to suppress leak detection, as some
538 # build tools (e.g., ninja) intentionally leak. We want leak checks when we run our tests, so
563 $(HOST_OUT_EXECUTABLES)/valgrind --leak-check=full --error-exitcode=1 \
[all...] |
| /bionic/libc/malloc_debug/ |
| README.md | 244 ### leak\_track
255 Example leak error found in the log:
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)
589 way you'll see the location of the leak directly without having to use
|
| /external/valgrind/ |
| FAQ.txt | 84 --run-libc-freeres=no option. You may then get space leak reports for
205 Also, for leak reports involving shared objects, if the shared object is
237 * A leak error message involving an unloaded shared object:
359 5.2. With Memcheck's memory leak detector, what's the difference between
384 * "suppressed" means that a leak error has been suppressed. There are
|
| /external/valgrind/docs/xml/ |
| FAQ.xml | 136 leak reports for glibc allocations (please don't report these to
296 <para>Also, for leak reports involving shared objects, if the shared
348 <para>A leak error message involving an unloaded shared object:</para>
519 <para>With Memcheck's memory leak detector, what's the
556 <para>"suppressed" means that a leak error has been suppressed.
|
| /external/clang/test/Driver/ |
| fsanitize.c | 73 // RUN: %clang -target x86_64-linux-gnu -fsanitize=leak,thread -pie -fno-rtti %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANL-SANT
74 // CHECK-SANL-SANT: '-fsanitize=leak' not allowed with '-fsanitize=thread'
76 // RUN: %clang -target x86_64-linux-gnu -fsanitize=leak,memory -pie -fno-rtti %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANL-SANM
77 // CHECK-SANL-SANM: '-fsanitize=leak' not allowed with '-fsanitize=memory'
88 // RUN: %clang -target x86_64-linux-gnu -fsanitize=kernel-address,leak -pie -fno-rtti %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANKA-SANL
89 // CHECK-SANKA-SANL: '-fsanitize=kernel-address' not allowed with '-fsanitize=leak'
95 // RUN: %clang -target x86_64-linux-gnu -fsanitize=efficiency-cache-frag,leak -pie -fno-rtti %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANE-SANL
96 // RUN: %clang -target x86_64-linux-gnu -fsanitize=efficiency-working-set,leak -pie -fno-rtti %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANE-SANL
97 // CHECK-SANE-SANL: '-fsanitize=efficiency-{{.*}}' not allowed with '-fsanitize=leak'
222 // RUN: %clang -target x86_64-linux-gnu -fsanitize=leak %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SAN
[all...] |
| /external/libxml2/doc/ |
| xml.html | [all...] |
| /external/jemalloc/ |
| ChangeLog | 37 - Fix a severe virtual memory leak. This regression was first released in
71 - Fix a file descriptor leak on Linux. This regression was first released in
119 - Scale leak report summary according to sampling probability. (@jasone)
202 a custom chunk allocation function. This resolves a virtual memory leak.
204 - Fix a potential tsd cleanup leak. (@cferris1000, @jasone)
536 - Fix a file descriptor leak in a prof_dump_maps() error path.
[all...] |
| /external/clang/test/Analysis/ |
| objc-arc.m | 94 CFDateRef date = CFDateCreate(0, t); // expected-warning {{Potential leak}}
145 id obj5 = (__bridge id)CFCreateSomething(); // expected-warning{{never read}} expected-warning{{leak}}
146 id obj6 = (__bridge NSString*)CFCreateString(); // expected-warning{{never read}} expected-warning{{leak}}
165 CFDateRef date = CFDateCreate(0, t); // expected-warning {{Potential leak}}
200 CFCreateString(); // expected-warning {{leak}}
214 NSObject *o = [[NSObject alloc] init]; // expected-warning {{leak}}
531 // CHECK-NEXT: <key>description</key><string>Potential leak of an object stored into 'date'</string>
533 // CHECK-NEXT: <key>type</key><string>Leak</string>
[all...] |
| /external/valgrind/docs/internals/ |
| 3_11_BUGSTATUS.txt | 109 358980 32 byte leak reported when code uses dlopen and links against pthread
177 354428 Bad report memory leak in OS X 10.11
332 15986 -> 16012 Add an optional 2nd arg to leak-autofreepool to test performance
396 16044 -> 16062 Further fixes following fix of leak in 16033
411 16043 -> 16069 Introduce leak-pool-3.* back into EXTRA_DIST as they are not
412 related to leak-autofreepool tests. This is a follow up
|
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Modules/ |
| gc_weakref.txt | 197 run tests, and convince yourself you don't have a leak.
201 code all you want and you won't find a reason for the leak.
|
| /external/clang/lib/StaticAnalyzer/Checkers/ |
| StreamChecker.cpp | 413 this, "Resource Leak",
414 "Opened File never closed. Potential Resource leak."));
|
| /external/clang/lib/StaticAnalyzer/Core/ |
| PlistDiagnostics.cpp | 442 // the leak location even after code is added between the allocation
443 // site and the end of scope (leak report location).
|
| /external/compiler-rt/lib/tsan/rtl/ |
| tsan_rtl_thread.cc | 162 ThreadLeak leak = {tctx, 1}; local
163 leaks.PushBack(leak);
|
| /external/curl/ |
| RELEASE-NOTES | 72 o openssl: fix memory leak of SSLKEYLOGFILE filename
91 o openssl: fix potential memory leak in SSLKEYLOGFILE logic
|
| /external/libvncserver/ |
| NEWS | 187 memory leaks squashed (localtime pseudo leak is still there :-)
201 initialize deferUpdateTime (memory "leak"!)
|
| /external/mesa3d/docs/relnotes/ |
| 10.1.1.html | 75 <li>gallium/util: Fix memory leak</li>
230 <li>r600g: Don't leak bytecode on shader compile failure</li>
|
| 12.0.4.html | 97 <li>i965/sync: Fix uninitalized usage and leak of mutex</li>
145 <li>pipe_loader_sw: Fix fd leak when instantiated via pipe_loader_sw_probe_kms</li>
|
| /external/python/cpython2/Modules/_ctypes/ |
| callbacks.c | 347 it alive forever - but a refcount and/or memory leak will
357 "memory leak in callback function."))
|
| /external/python/cpython2/Modules/ |
| gc_weakref.txt | 197 run tests, and convince yourself you don't have a leak.
201 code all you want and you won't find a reason for the leak.
|
| /external/python/cpython3/Modules/ |
| gc_weakref.txt | 197 run tests, and convince yourself you don't have a leak.
201 code all you want and you won't find a reason for the leak.
|
| /external/swiftshader/third_party/llvm-subzero/lib/Support/Unix/ |
| Signals.inc | 122 // reported as a leak. We don't make any attempt to remove our alt signal
142 NewAltStackPointer = AltStack.ss_sp; // Save to avoid reporting a leak.
|
