MantisBT - OCaml
View Issue Details
0004900OCaml~DO NOT USE (was: OCaml general)public2009-10-26 08:382009-10-26 14:36
0004900: max_overhead vs. caml_gc_major / caml_gc_full_major
I noticed this morning that gc_ctrl.c:test_and_compact, called from caml_gc_major and caml_gc_full_major, appears to be able to call caml_compact_heap (which doesn't test caml_percent_max) in the situation where the first calculation of fp yields >=1_000_000, caml_percent_max is set to 1_000_000, and there is more than one heap chunk.

Is the setting of caml_percent_max (aka max_overhead) to 1_000_000 not supposed to prevent automatic compaction in all cases? I wonder if the test in that function should be "fp > caml_percent_max", or whether 1_000_000 - 1 should be used for the saturating calculation.
No tags attached.
Issue History
2009-10-26 08:38shinwellNew Issue
2009-10-26 14:36doligezNote Added: 0005142
2009-10-26 14:36doligezStatusnew => closed
2009-10-26 14:36doligezFixed in Version => 3.11.2+dev
2017-02-23 16:36doligezCategoryOCaml general => -OCaml general
2017-03-03 17:55doligezCategory-OCaml general => -(deprecated) general
2017-03-03 18:01doligezCategory-(deprecated) general => ~deprecated (was: OCaml general)
2017-03-06 17:04doligezCategory~deprecated (was: OCaml general) => ~DO NOT USE (was: OCaml general)

2009-10-26 14:36   
well spotted