This is documented, and here is one way to get the documentation: export invalid MONO_GC_PARAMS , run mono :
export MONO_GC_PARAMS=xxx mono sample.exe
and get help:
Warning: In environment variable `MONO_GC_PARAMS': Unknown option `xxx`. - Ignoring. MONO_GC_PARAMS must be a comma-delimited list of one or more of the following: max-heap-size=N (where N is an integer, possibly with ak, m or ag suffix) soft-heap-limit=n (where N is an integer, possibly with ak, m or ag suffix) nursery-size=N (where N is an integer, possibly with ak, m or ag suffix) major=COLLECTOR (where COLLECTOR is `marksweep', `marksweep-conc', `marksweep-par', 'marksweep-fixed' or 'marksweep-fixed-par') minor=COLLECTOR (where COLLECTOR is `simple' or `split') wbarrier=WBARRIER (where WBARRIER is `remset' or `cardtable') stack-mark=MARK-METHOD (where MARK-METHOD is 'precise' or 'conservative') [no-]cementing evacuation-threshold=P (where P is a percentage, an integer in 0-100) (no-)lazy-sweep Experimental options: save-target-ratio=R (where R must be between 0.10 - 2.00). default-allowance-ratio=R (where R must be between 1.00 - 10.00).
As you can see, max-heap-size is specified, not in Experimental Options . Therefore, I would say that it is safe.
Stephane delcroix
source share