/external/chromium/chrome/browser/ui/cocoa/ |
about_window_controller_unittest.mm | 119 // because it leaks restart dialogs. If the About box is revised to use
|
task_manager_mac_unittest.mm | 39 // Test creation, to ensure nothing leaks or crashes.
|
/external/chromium/chrome/browser/ui/cocoa/find_bar/ |
find_bar_text_field_cell_unittest.mm | 60 // Test drawing, mostly to ensure nothing leaks or crashes.
|
/external/chromium_org/base/threading/ |
worker_pool.cc | 108 // Do not report PostTaskAndReplyRelay leaks in tests. There's nothing we can
|
/external/chromium_org/chrome/browser/chromeos/policy/ |
policy_cert_service.cc | 73 // data is absolutely confined to the managed profile and never, ever leaks to
|
/external/chromium_org/chrome/browser/ui/cocoa/bookmarks/ |
bookmark_bar_toolbar_view_unittest.mm | 110 // Test drawing, mostly to ensure nothing leaks or crashes.
|
/external/chromium_org/chrome/browser/ui/cocoa/find_bar/ |
find_bar_text_field_cell_unittest.mm | 57 // Test drawing, mostly to ensure nothing leaks or crashes.
|
/external/chromium_org/chrome/browser/ui/cocoa/ |
menu_button_unittest.mm | 103 // Test assigning a menu, again mostly to ensure nothing leaks or crashes.
|
task_manager_mac_unittest.mm | 49 // Test creation, to ensure nothing leaks or crashes.
|
/external/chromium_org/chrome/common/extensions/docs/examples/extensions/plugin_settings/js/ |
plugin_settings_test.html | 136 // Clear local storage and |rules_| to make sure no state leaks into the next
|
/external/chromium_org/content/public/test/ |
test_browser_thread_bundle.cc | 23 // To avoid memory leaks, we must ensure that any tasks posted to the blocking
|
/external/chromium_org/content/test/plugin/ |
plugin_npobject_lifetime_test.cc | 30 // TODO: this propery leaks.
|
/external/chromium_org/skia/ext/ |
refptr.h | 13 // this class to avoid dealing with the ref-counting and prevent leaks/crashes
|
/external/chromium_org/third_party/mesa/src/docs/ |
relnotes-7.6.1.html | 67 <li>Fixed assorted memory leaks (usually on error paths)
|
/external/chromium_org/third_party/opus/src/celt/ |
kiss_fft.h | 104 * The returned value should be free()d when done to avoid memory leaks.
|
/external/chromium_org/third_party/sqlite/src/test/ |
sidedelete.test | 69 # This will cause stacks leaks but not database corruption prior
|
/external/chromium_org/third_party/tcmalloc/chromium/src/ |
static_vars.cc | 67 // which leads to it missing some memory leaks.
|
/external/chromium_org/third_party/tcmalloc/vendor/doc/ |
heapprofile.html | 23 <li> Locating memory leaks 145 <H2>Checking for Leaks</H2> 147 <p>You can use the heap profiler to manually check for leaks, for 214 of a program so you can find gradual memory leaks. One simple way to
|
/external/chromium_org/third_party/tcmalloc/vendor/src/gperftools/ |
heap-profiler.h | 89 * memory leaks. Will include the reason in the logged message
|
/external/chromium_org/third_party/tcmalloc/vendor/src/ |
static_vars.cc | 67 // which leads to it missing some memory leaks.
|
/external/clang/test/Analysis/inlining/ |
RetainCountExamples.m | 36 // Test that retain release checker warns on leaks and use-after-frees when
|
/external/jmonkeyengine/engine/src/test/jme3test/stress/ |
TestLeakingGL.java | 48 * Generates 400 new meshes every frame then leaks them.
|
/external/llvm/include/llvm/Support/ |
LeakDetector.h | 55 /// remove'd, big obnoxious warnings about memory leaks are issued.
|
/external/llvm/lib/IR/ |
LeakDetector.cpp | 64 << "delete it. Please check your code for memory leaks.\n";
|
LeaksContext.h | 11 // LLVMContextImpl for leaks detectors.
|