HomeSort by relevance Sort by last modified time
    Searched full:leak (Results 1026 - 1050 of 2655) sorted by null

<<41424344454647484950>>

  /prebuilts/clang/host/darwin-x86/clang-4691093/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4053586/prebuilt_include/clang/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4393122/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4479392/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4579689/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4630689/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4639204/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/clang/host/linux-x86/clang-4691093/include/clang/Analysis/Support/
BumpVector.h 242 // For now, leak 'Begin'. We can add it back to a freelist in
  /prebuilts/go/darwin-x86/src/cmd/go/internal/envcmd/
env.go 112 // ExtraEnvVars returns environment variables that should not leak into child processes.
  /prebuilts/go/darwin-x86/src/runtime/
mgcsweepbuf.go 98 // leak because even a 1TB heap would waste
  /prebuilts/go/linux-x86/src/cmd/go/internal/envcmd/
env.go 112 // ExtraEnvVars returns environment variables that should not leak into child processes.
  /prebuilts/go/linux-x86/src/runtime/
mgcsweepbuf.go 98 // leak because even a 1TB heap would waste
  /prebuilts/ndk/r16/sources/third_party/googletest/googletest/samples/
sample5_unittest.cc 41 // make sure that all tests for a GUI library don't leak important
  /prebuilts/tools/darwin-x86_64/protoc/include/google/protobuf/stubs/
common.h 180 // * You use a draconian definition of "memory leak" in which you expect
  /system/chre/chre_api/legacy/v1_0/
chre.h 79 * where otherwise a CHRE implementation is likely to leak memory. Similarly,
  /system/core/libcutils/
str_parms.cpp 36 * false warnings about potential memory leak.
  /system/core/trusty/keymaster/
Makefile 132 MEMCHECK_OPTS=--leak-check=full \
  /system/update_engine/common/
subprocess_unittest.cc 270 // This test would leak a callback that runs when the child process exits
  /system/update_engine/payload_consumer/
filesystem_verifier_action_unittest.cc 297 // TerminateEarlyTest may leak some null callbacks from the Stream class.
  /external/clang/test/Analysis/
retain-release-path-notes-gc.m 44 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}}
67 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' and returned from method 'getViolation' is potentially leaked when using garbage collection. Callers of this method do not expect a returned object with a +1 retain count since they expect the object to be managed by the garbage collector}}
72 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' and returned from method 'copyViolation' is potentially leaked when using garbage collection. Callers of this method do not expect a returned object with a +1 retain count since they expect the object to be managed by the garbage collector}}
208 // CHECK-NEXT: <key>description</key><string>Potential leak (when using garbage collection) of an object stored into &apos;leaked&apos;</string>
210 // CHECK-NEXT: <key>type</key><string>Leak of object when using garbage collection</string>
    [all...]
retain-release.mm 288 id x = [[NSObject alloc] init]; // expected-warning {{leak}}
404 // Previously this reported a bogus leak.
460 mStr.reset( CFStringCreateCopy( 0, str1.get() ) ); //expected-warning {{Potential leak of an object}}
  /external/kmod/
NEWS 95 - Fix leak in depmod when -b flag is passed multiple times
315 - Fix memory leak in hash implementation
401 - Fix leak in index when there's a partial match
  /external/libxml2/doc/
xmlmem.html 64 memory leak during the full regression test sequence, this helps a lot
65 ensuring that libxml2 does not leak memory and bullet proof memory
67 resulting in major portability problems!).</p><p>If the .memdump reports a leak, it displays the allocation function and
  /external/libxml2/xstc/
xstc.py 58 opa.add_option("--rmleo", "--report-mem-leak-errors-only", action="store_true",
60 help="Display erroneous tests of type 'memory leak' only")
313 self.log.append("%s + memory leak: %d bytes\n" % (self.name, self.memLeak))
  /external/v8/include/
v8-util.h 319 static PersistentContainerValue Leak(Global<V>* persistent) {
411 *reference = this->Leak(&value);
483 *reference = this->Leak(&value);

Completed in 1321 milliseconds

<<41424344454647484950>>