Bug 36929 - try to keep finalizer queue smaller
Summary: try to keep finalizer queue smaller
Alias: None
Product: Runtime
Classification: Mono
Component: GC (show other bugs)
Version: unspecified
Hardware: All All
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2015-12-11 23:05 UTC by Bernhard Urban
Modified: 2018-02-23 20:21 UTC (History)
6 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:


Description Bernhard Urban 2015-12-11 23:05:26 UTC
On devices with smaller memory we can get the runtime bail out:
$ MONO_GC_DEBUG=bridge=Bridge MONO_GC_PARAMS=minor=split MONO_ENV_OPTIONS=--gc=sgen MONO_PATH=/home/lewurm/monoperf/mono/mcs/class/lib/net_4_x ../../mono/mini/mono sgen-bridge-major-fragmentation.exe --optimize=all —debug
Error: Garbage collector could not allocate 6053368 bytes of memory for finalize-ready.

that's around 1.5 million objects in that queue, the test application generates around 2 million objects with a finalizer. the question is if the GC should really wait that long or do something about it earlier (and thus free up memory).
Comment 1 Alex Rønne Petersen 2016-08-29 09:33:15 UTC
Marking as CONFIRMED and enhancement.

Note You need to log in before you can comment on or make changes to this bug.