Lines Matching full:leak
47 Memcheck can also produce XTree leak reports using the Callgrind file
87 - New command line options --xtree-leak=no|yes and --xtree-leak-file=<file>
88 to produce the end of execution leak report in a xtree callgrind format
92 the leak report in an xtree file.
227 377717 Fix massive space leak when reading compressed debuginfo sections
571 - The default value for --leak-check-heuristics has been changed from
760 339755 Fix known deliberate memory leak in setenv() on Mac OS X 10.9
799 343303 Fix known deliberate memory leak in setenv() on Mac OS X 10.10
807 343663 OS X 10.10 Memchecj always reports a leak regardless of [..]
870 347379 valgrind --leak-check=full leak errors from system libs on OS X 10.8
1055 - Leak checker: there is a new leak check heuristic called
1087 memory leak when a lot of Ada tasks are created and terminated.
1314 337528 leak check heuristic for block prefixed by length as 64bit number
1395 - Better control over the leak checker. It is now possible to
1396 specify which leak kinds (definite/indirect/possible/reachable)
1398 should be suppressed by a given leak suppression. This is done
1399 using the options --show-leak-kinds=kind1,kind2,..,
1400 --errors-for-leak-kinds=kind1,kind2,.. and an optional
1401 "match-leak-kinds:" line in suppression entries, respectively.
1403 Note that generated leak suppressions contain this new line and
1405 same behaviour as previous releases, remove the "match-leak-kinds:"
1408 - Reduced "possible leak" reports from the leak checker by the use
1414 option --leak-check-heuristics=heur1,heur2,...
1423 - Better reporting of leak suppression usage. The list of used
1425 each leak suppressions, how many blocks and bytes it suppressed
1426 during the last leak search.
1709 324227 memcheck false positive leak when a thread calls exit+block [..]
1847 the addresses/sizes of the blocks of a leak search loss record.
1859 - Performance of memory leak check has been improved, especially in
1861 rules used to suppress leak reports.
2168 (--join-list-vol); fixed a memory leak triggered by repeated client
2414 188572 Valgrind on Mac should suppress setenv() mem leak
2572 is enabled by default. When disabled, the leak detector will not
2676 206600 Leak checker fails to upgrade indirect blocks when their
2739 247561 Some leak testcases fails due to reachable addresses in
2790 * Improvements and simplifications to Memcheck's leak checker.
2858 * Memcheck's leak checker has been improved.
2860 - The results for --leak-check=summary now match the summary results
2861 for --leak-check=full. Previously they could differ because
2862 --leak-check=summary counted "indirectly lost" blocks and
2870 - The default value for the --leak-resolution option has been
2872 leak reports will be produced, but each leak report will describe
2875 - With --leak-check=full, "definitely lost" and "possibly lost"
2879 --leak-check=summary is specified, however.
2881 - Documentation for the leak checker has been improved.
2891 noticeable with Memcheck, where the leak summary now occurs before
2893 counted as proper errors (see the description of the leak checker
3127 * exp-Omega, an experimental instantaneous leak-detecting tool, was
3193 100628 leak-check gets assertion failure when using
3211 137904 Valgrind reports a memory leak when using POSIX threads,
3216 148441 (wine) can't find memory leak in Wine, win32 binary
3218 148742 Leak-check fails assert on exit
3221 152393 leak errors produce an exit code of 0. I need some way to
3222 cause leak errors to result in a nonzero exit code.
3223 157154 documentation (leak-resolution doc speaks about num-callers
3267 188572 Valgrind on Mac should suppress setenv() mem leak
3290 195069 memcheck: reports leak (memory still reachable) for
3306 197929 Make --leak-resolution=high the default
3307 197930 Reduce spacing between leak reports
3332 n-i-bz drd: fixed a memory leak triggered by vector clock deallocation
3461 * exp-Omega, an experimental instantaneous leak-detecting tool, is no