HomeSort by relevance Sort by last modified time
    Searched full:leak (Results 701 - 725 of 1447) sorted by null

<<21222324252627282930>>

  /external/chromium/googleurl/src/
url_util.h 57 // Cleanup is not required, except some strings may leak. For most user
  /external/chromium/third_party/libjingle/source/talk/base/
messagequeue.cc 77 // we don't leak this object at program shutdown. As mentioned above, this is
  /external/chromium_org/base/allocator/
allocator_shim.cc 304 // We intentionally leak this object. It lasts for the process
  /external/chromium_org/base/android/
jni_android.cc 50 // Leak the global app context, as it is used from a non-joinable worker thread
  /external/chromium_org/chrome/browser/safe_browsing/
malware_details.cc 38 // don't leak it.
safe_browsing_store_unittest_helper.cc 77 // Chunk numbers shouldn't leak over.
  /external/chromium_org/chrome/browser/sync_file_system/local/
syncable_file_operation_runner_unittest.cc 329 // This shouldn't crash nor leak memory.
  /external/chromium_org/chrome/installer/linux/common/
installer.include 40 # Note that this function is run in a sub-shell so we don't leak this
  /external/chromium_org/components/nacl/loader/
nacl_ipc_adapter_unittest.cc 41 // task gets run, or it will appear as a leak.
  /external/chromium_org/content/browser/
plugin_process_host.cc 118 // leak HWNDs, we should destroy existing plugin parent windows.
  /external/chromium_org/content/public/test/
test_launcher.cc 122 // Some of the below method calls will leak objects if there is no
  /external/chromium_org/content/renderer/pepper/
plugin_module.h 200 // In production we purposely leak the HostGlobals object but in unittest
plugin_object.cc 203 // all identifiers leak anyway :( .
  /external/chromium_org/gpu/command_buffer/client/
gl_in_process_context.cc 316 // those resources might leak. Also, any remaining side effects of commands
  /external/chromium_org/net/disk_cache/
stress_cache.cc 223 // We leak everything here :)
  /external/chromium_org/third_party/WebKit/Source/core/svg/graphics/
SVGImage.cpp 334 // FIXME: If this SVG ends up loading itself, we might leak the world.
  /external/chromium_org/third_party/angle_dx11/src/compiler/
PoolAlloc.h 152 // by calling pop(), and to not have to solve memory leak problems.
  /external/chromium_org/third_party/libjingle/source/talk/base/
messagequeue.cc 73 // we don't leak this object at program shutdown. As mentioned above, this is
nssidentity.cc 348 // Assign to a scoped_ptr so we don't leak on error.
  /external/chromium_org/third_party/libxml/src/
check-relaxng-test-suite.py 393 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
check-relaxng-test-suite2.py 417 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
check-xsddata-test-suite.py 419 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
  /external/chromium_org/third_party/mesa/src/docs/
relnotes-8.0.4.html 152 <li>glsl: Hook up loop_variable_state destructor to plug a memory leak.</li>
  /external/chromium_org/third_party/openssl/openssl/crypto/ecdsa/
ecs_ossl.c 147 /* We do not want timing information to leak the length of k,
  /external/chromium_org/third_party/skia/src/views/
SkEvent.cpp 287 // leak this, so we don't incure any shutdown perf hit

Completed in 1517 milliseconds

<<21222324252627282930>>