Lines Matching full:leak
70 ??Memcheck?can?also?produce?XTree?leak?reports?using?the?Callgrind?file<br>
110 ??-?New?command?line?options?--xtree-leak=no|yes?and?--xtree-leak-file=<file><br>
111 ????to?produce?the?end?of?execution?leak?report?in?a?xtree?callgrind?format<br>
115 ????the?leak?report?in?an?xtree?file.<br>
250 377717??Fix?massive?space?leak?when?reading?compressed?debuginfo?sections<br>
594 ??-?The?default?value?for?--leak-check-heuristics?has?been?changed?from<br>
783 339755??Fix?known?deliberate?memory?leak?in?setenv()?on?Mac?OS?X?10.9<br>
822 343303??Fix?known?deliberate?memory?leak?in?setenv()?on?Mac?OS?X?10.10<br>
830 343663??OS?X?10.10??Memchecj?always?reports?a?leak?regardless?of?[..]<br>
893 347379??valgrind?--leak-check=full?leak?errors?from?system?libs?on?OS?X?10.8<br>
1078 ??-?Leak?checker:?there?is?a?new?leak?check?heuristic?called<br>
1110 ????memory?leak?when?a?lot?of?Ada?tasks?are?created?and?terminated.<br>
1337 337528??leak?check?heuristic?for?block?prefixed?by?length?as?64bit?number<br>
1418 ??-?Better?control?over?the?leak?checker.??It?is?now?possible?to<br>
1419 ????specify?which?leak?kinds?(definite/indirect/possible/reachable)<br>
1421 ????should?be?suppressed?by?a?given?leak?suppression.??This?is?done<br>
1422 ????using?the?options?--show-leak-kinds=kind1,kind2,..,<br>
1423 ????--errors-for-leak-kinds=kind1,kind2,..?and?an?optional<br>
1424 ????"match-leak-kinds:"?line?in?suppression?entries,?respectively.<br>
1426 ????Note?that?generated?leak?suppressions?contain?this?new?line?and<br>
1428 ????same?behaviour?as?previous?releases,?remove?the?"match-leak-kinds:"<br>
1431 ??-?Reduced?"possible?leak"?reports?from?the?leak?checker?by?the?use<br>
1437 ????option?--leak-check-heuristics=heur1,heur2,...<br>
1446 ??-?Better?reporting?of?leak?suppression?usage.??The?list?of?used<br>
1448 ????each?leak?suppressions,?how?many?blocks?and?bytes?it?suppressed<br>
1449 ????during?the?last?leak?search.<br>
1732 324227??memcheck?false?positive?leak?when?a?thread?calls?exit+block?[..]<br>
1870 ????the?addresses/sizes?of?the?blocks?of?a?leak?search?loss?record.<br>
1882 ??-?Performance?of?memory?leak?check?has?been?improved,?especially?in<br>
1884 ????rules?used?to?suppress?leak?reports.<br>
2191 ??(--join-list-vol);?fixed?a?memory?leak?triggered?by?repeated?client<br>
2437 188572??Valgrind?on?Mac?should?suppress?setenv()?mem?leak<br>
2595 ??is?enabled?by?default.??When?disabled,?the?leak?detector?will?not<br>
2699 206600??Leak?checker?fails?to?upgrade?indirect?blocks?when?their<br>
2762 247561??Some?leak?testcases?fails?due?to?reachable?addresses?in<br>
2813 *?Improvements?and?simplifications?to?Memcheck's?leak?checker.<br>
2881 *?Memcheck's?leak?checker?has?been?improved.??<br>
2883 ??-?The?results?for?--leak-check=summary?now?match?the?summary?results<br>
2884 ????for?--leak-check=full.??Previously?they?could?differ?because<br>
2885 ????--leak-check=summary?counted?"indirectly?lost"?blocks?and<br>
2893 ??-?The?default?value?for?the?--leak-resolution?option?has?been<br>
2895 ????leak?reports?will?be?produced,?but?each?leak?report?will?describe<br>
2898 ??-?With?--leak-check=full,?"definitely?lost"?and?"possibly?lost"<br>
2902 ????--leak-check=summary?is?specified,?however.<br>
2904 ??-?Documentation?for?the?leak?checker?has?been?improved.<br>
2914 ????noticeable?with?Memcheck,?where?the?leak?summary?now?occurs?before<br>
2916 ????counted?as?proper?errors?(see?the?description?of?the?leak?checker<br>
3150 *?exp-Omega,?an?experimental?instantaneous?leak-detecting?tool,?was<br>
3216 100628??leak-check?gets?assertion?failure?when?using?<br>
3234 137904??Valgrind?reports?a?memory?leak?when?using?POSIX?threads,<br>
3239 148441??(wine)?can't?find?memory?leak?in?Wine,?win32?binary?<br>
3241 148742??Leak-check?fails?assert?on?exit?<br>
3244 152393??leak?errors?produce?an?exit?code?of?0.?I?need?some?way?to?<br>
3245 ????????cause?leak?errors?to?result?in?a?nonzero?exit?code.?<br>
3246 157154??documentation?(leak-resolution?doc?speaks?about?num-callers<br>
3290 188572??Valgrind?on?Mac?should?suppress?setenv()?mem?leak?<br>
3313 195069??memcheck:?reports?leak?(memory?still?reachable)?for?<br>
3329 197929??Make?--leak-resolution=high?the?default?<br>
3330 197930??Reduce?spacing?between?leak?reports?<br>
3355 n-i-bz??drd:?fixed?a?memory?leak?triggered?by?vector?clock?deallocation<br>
3484 *?exp-Omega,?an?experimental?instantaneous?leak-detecting?tool,?is?no<br>
