In the spirit of other changes over the past month aimed at supporting
monster-sized programs better, increase the default freelist volume
from 1M to 5M.  Maybe even that is too small.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4954 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/docs/valgrind.1 b/docs/valgrind.1
index f303b48..fbe7fd7 100644
--- a/docs/valgrind.1
+++ b/docs/valgrind.1
@@ -308,7 +308,7 @@
 
 .TP
 .B
---freelist-vol=<number> [default: 1000000]
+--freelist-vol=<number> [default: 5000000]
 When the client program releases memory using free (in C) or delete
 (C++), that memory is not immediately made available for re-allocation.
 Instead it is marked inaccessible and placed in a queue of freed blocks.
diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index f7b2dcc..ea1d363 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -120,7 +120,7 @@
 
   <listitem id="freelist">
     <para><computeroutput>--freelist-vol=&lt;number></computeroutput>
-    [default: 1000000]</para>
+    [default: 5000000]</para>
     <para>When the client program releases memory using free (in
     <literal>C</literal>) or delete (<literal>C++</literal>),
     that memory is not immediately made available for
diff --git a/memcheck/mac_shared.c b/memcheck/mac_shared.c
index 2e0449e..fb6b01a 100644
--- a/memcheck/mac_shared.c
+++ b/memcheck/mac_shared.c
@@ -59,7 +59,7 @@
 /*------------------------------------------------------------*/
 
 Bool          MAC_(clo_partial_loads_ok)       = True;
-Int           MAC_(clo_freelist_vol)           = 1000000;
+Int           MAC_(clo_freelist_vol)           = 5000000;
 LeakCheckMode MAC_(clo_leak_check)             = LC_Summary;
 VgRes         MAC_(clo_leak_resolution)        = Vg_LowRes;
 Bool          MAC_(clo_show_reachable)         = False;
@@ -101,7 +101,7 @@
 "    --leak-resolution=low|med|high   how much bt merging in leak check [low]\n"
 "    --show-reachable=no|yes          show reachable blocks in leak check? [no]\n"
 "    --partial-loads-ok=no|yes        too hard to explain here; see manual [yes]\n"
-"    --freelist-vol=<number>          volume of freed blocks queue [1000000]\n"
+"    --freelist-vol=<number>          volume of freed blocks queue [5000000]\n"
 "    --workaround-gcc296-bugs=no|yes  self explanatory [no]\n"
    );
    VG_(replacement_malloc_print_usage)();