aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/lsan.supp
Commit message (Collapse)AuthorAge
* Suppress mystery leak.Gravatar mtklein2014-09-05
| | | | | | | | | BUG=skia:2916 R=caryclark@google.com, mtklein@google.com Author: mtklein@chromium.org Review URL: https://codereview.chromium.org/543063002
* Update LSAN suppressions.Gravatar mtklein2014-08-29
| | | | | | | | | | | | | | | | | | | | | | | | | Seems the obvious thing works now. Ran nanobench, ----------------------------------------------------- Suppressions used: count bytes template 586 3530064 libGL.so ----------------------------------------------------- and dm, ----------------------------------------------------- Suppressions used: count bytes template 340 2048160 libGL.so ----------------------------------------------------- BUG=skia: R=robertphillips@google.com, mtklein@google.com Author: mtklein@chromium.org Review URL: https://codereview.chromium.org/517133002
* Add a suppressions file for leak sanitizer.Gravatar commit-bot@chromium.org2014-01-23
LeakSanitizer is built into AddressSanitizer, and runs with no extra speed penalty. Most interestingly, it's got a lock-free allocator, so it doesn't bottleneck threaded code. This file is enough to supress all leak warnings except from the Nvidia driver on my desktop for tests and dm. Looks like lsan doesn't or can't pay attention to leaked globals (-fno-common doesn't affect this). BUG=skia: R=robertphillips@google.com Author: mtklein@google.com Review URL: https://codereview.chromium.org/145033010 git-svn-id: http://skia.googlecode.com/svn/trunk@13153 2bbb7eff-a529-9590-31e7-b0007b416f81