diff options
| author | Evan Huus <eapache@gmail.com> | 2014-06-24 18:30:23 -0400 |
|---|---|---|
| committer | Michael Mann <mmann78@netscape.net> | 2014-06-24 23:43:28 +0000 |
| commit | 3a943e9254a597b4afca74b7912bb4d33bc299ea (patch) | |
| tree | 32b8b882dd9a16e4191bee7bd36557016d671806 /tools | |
| parent | 29ecd114bfd3ba01ee340ffa084eeeafb886f750 (diff) | |
Reduce maximum permitted leakage to 100KB
Down from 500KB. The old value only triggered once that I can recall, and the
"average" leakage I'm seeing on most captures is only a few KB now, so this
shouldn't flood us with issues (which was the original concern leaving it so
high).
Change-Id: Ie4c98696b3fb7a533a7dc4f83c7ac8c458b499c8
Reviewed-on: https://code.wireshark.org/review/2633
Reviewed-by: Michael Mann <mmann78@netscape.net>
Diffstat (limited to 'tools')
| -rwxr-xr-x | tools/fuzz-test.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/fuzz-test.sh b/tools/fuzz-test.sh index d3922c2e3e..4c625cca33 100755 --- a/tools/fuzz-test.sh +++ b/tools/fuzz-test.sh @@ -48,7 +48,7 @@ VALGRIND=0 # The maximum permitted amount of memory leaked. Eventually this should be # worked down to zero, but right now that would fail on every single capture. # Only has effect when running under valgrind. -MAX_LEAK=`expr 1024 \* 500` +MAX_LEAK=`expr 1024 \* 100` # To do: add options for file names and limits while getopts ":2b:C:d:e:gp:P:" OPTCHAR ; do |