HomeSort by relevance Sort by last modified time
    Searched full:leaks (Results 426 - 450 of 776) sorted by null

<<11121314151617181920>>

  /external/chromium_org/chrome/browser/profiles/
profile_info_cache_unittest.cc 98 // memory leaks.
  /external/chromium_org/chrome/browser/ui/cocoa/tabs/
tab_controller_unittest.mm 244 [[controller view] display]; // Test drawing to ensure nothing leaks/crashes.
  /external/chromium_org/chrome/browser/ui/views/accessibility/
accessibility_event_router_views_unittest.cc 136 // forces it to be deleted now, so we don't have any memory leaks
  /external/chromium_org/chrome/common/extensions/docs/templates/json/
chrome_sidenav.json 147 "title": "Uncovering DOM Leaks",
  /external/chromium_org/chrome/installer/setup/
install_unittest.cc 51 // Clean up test directory manually so we can fail if it leaks.
setup_util_unittest.cc 42 // Clean up test directory manually so we can fail if it leaks.
  /external/chromium_org/content/browser/gamepad/
xbox_data_fetcher_mac.cc 273 // contain more interfaces, this will serve to avoid memory leaks.)
  /external/chromium_org/content/common/gpu/client/
command_buffer_proxy_impl.cc 487 // called, leading to stalled threads and/or memory leaks.
  /external/chromium_org/content/ppapi_plugin/
ppapi_thread.cc 464 // Note: This leaks memory, which is expected behavior.
  /external/chromium_org/courgette/
courgette_tool.cc 455 // '-repeat=N' is for debugging. Running many iterations can reveal leaks and
  /external/chromium_org/gpu/command_buffer/service/
query_manager.cc 551 // callbacks to avoid leaks.
  /external/chromium_org/net/cert/
multi_threaded_cert_verifier.cc 254 // memory leaks or worse errors.
  /external/chromium_org/net/proxy/
dhcp_proxy_script_fetcher_win_unittest.cc 110 // them a little time. If we start running into Valgrind leaks, we can
  /external/chromium_org/ppapi/api/
ppb_message_loop.idl 117 * associated memory to avoid leaks. If you're using the C++
  /external/chromium_org/ppapi/c/
ppb_message_loop.h 135 * associated memory to avoid leaks. If you're using the C++
  /external/chromium_org/ppapi/cpp/
message_loop.h 122 /// associated memory to avoid leaks. If you're using the C++
  /external/chromium_org/ppapi/tests/
test_case.h 224 // Var ids that should be ignored when checking for leaks on shutdown.
  /external/chromium_org/third_party/WebKit/Tools/Scripts/webkitpy/common/net/buildbot/
buildbot_unittest.py 215 <h1>Directory listing for /results/SnowLeopard Intel Leaks/</h1>
  /external/chromium_org/third_party/icu/source/i18n/
digitlst.h 59 // No direct access to the MaybeStackHeaderAndArray leaks out of the i18n library.
  /external/chromium_org/third_party/icu/source/i18n/unicode/
ucsdet.h 79 * memory leaks in the application.
  /external/chromium_org/third_party/libjingle/source/talk/base/
task_unittest.cc 554 // Note: this leaks memory, so don't do this.
  /external/chromium_org/third_party/libxml/src/
xmlcatalog.c 603 * Cleanup and check for memory leaks
  /external/chromium_org/third_party/mesa/src/docs/
relnotes-8.0.3.html 304 <li>swrast: Fix memory leaks in blit_linear.</li>
  /external/chromium_org/third_party/mesa/src/src/gallium/auxiliary/gallivm/
lp_bld_init.c 319 * memory leaks and false cache hits when these objects are destroyed.
  /external/chromium_org/third_party/openssl/openssl/crypto/srp/
srp_vfy.c 455 /* there may be still some leaks to fix, if this fails, the application terminates most likely */

Completed in 955 milliseconds

<<11121314151617181920>>