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

<<51525354555657585960>>

  /external/libchrome/base/metrics/
statistics_recorder.cc 519 // We are going to leak the histograms and the ranges.
  /external/libchrome/base/process/
launch.h 81 // leak to the child process, causing errors such as open socket hangs.
  /external/libchrome/base/threading/
sequenced_worker_pool.h 211 // deliberately leak it.
  /external/libjpeg-turbo/
change.log 164 no longer leak memory.
  /external/libmojo/base/android/jni_generator/java/src/org/chromium/example/jni_generator/
SampleForTests.java 53 // ref implies a new GC root, so be sure it will not leak and it must never rely on being
  /external/libpcap/
optimize.c     [all...]
  /external/libxml2/doc/devhelp/
libxml2-threads.html 95 </pre><p>xmlCleanupThreads() is used to to cleanup all the thread related data of the libxml2 library once processing has ended. WARNING: if your application is multithreaded or has plugin support calling this may crash the application if another thread or a plugin is still using libxml2. It's sometimes very hard to guess if libxml2 is in use in the application, some libraries or plugins may use it without notice. In case of doubt abstain from calling this function or do it just before calling exit() to avoid leak reports from valgrind !</p>
  /external/libxml2/python/tests/
reader.py 445 print("Memory leak %d bytes" % (libxml2.debugMemory(1)))
  /external/libxml2/
runxmlconf.c 165 * for every test, since it will confuse the memory leak detection.
  /external/llvm/lib/Analysis/
CaptureTracking.cpp 241 // its return value and doesn't unwind (a readonly function can leak bits
  /external/llvm/lib/Support/Unix/
Signals.inc 123 // Hold onto the old alternate signal stack so that it's not reported as a leak.
  /external/ltp/testcases/kernel/syscalls/symlink/
symlink01.c     [all...]
  /external/mesa3d/docs/relnotes/
9.0.2.html 181 <li>i965/gen4: Fix memory leak each time compile_gs_prog() is called.</li>
9.0.3.html 206 <li>gallium/u_upload_mgr: fix a serious memory leak</li>
9.1.4.html 135 <li>u_vbuf: fix index buffer leak</li>
  /external/mesa3d/src/gallium/drivers/svga/
svga_pipe_sampler.c 391 * SVGA3D_vgpu10_DestroyShaderResourceView() and leak the sampler
  /external/mesa3d/src/mapi/glapi/
glapi_getproc.c 468 /* FIXME: Possible memory leak here. */
  /external/mksh/src/
os2.c 326 /*XXX memory leak */
  /external/pdfium/fxjs/xfa/
cjx_layoutpseudomodel.cpp 376 // TODO(dsinclair): Who owns the array once we release it? Won't this leak?
  /external/ppp/pppd/
upap.c 436 /* We do not want to leak info about the pap result. */
  /external/python/cpython2/Lib/test/
lock_tests.py 138 # The lock shouldn't leak a Thread instance when used from a foreign
test_bsddb.py 259 # do the bsddb._DBWithCursor iterator internals leak cursors?
test_subprocess.py 425 # Test for the fd leak reported in http://bugs.python.org/issue2791.
545 # Make sure we leak no resources
721 """Test for the fork() failure fd leak reported in issue16327."""
    [all...]
  /external/python/cpython2/Lib/wsgiref/
handlers.py 441 # Do not allow os.environ to leak between requests in Google App Engine
  /external/python/cpython2/Misc/
SpecialBuilds.txt 25 there's probably a leak. Remember, though, that in interactive mode the special

Completed in 891 milliseconds

<<51525354555657585960>>