Part of the computational workload shouldered by Extremem is to track the total allocations performed by each thread along with tracking when previously allocated objects should become eligible for garbage collection. These tallies are reported to standard output.
Nearly all objects allocated by Extremem are eventually supposed to be discarded. At certain critical execution points, the total number and flavors of certain object allocations should equal the total number and flavors of matching object discards. That these numbers do not currently match demonstrates that there are errors in the current calculations of these memory allocation and deallocation tallies.
We need to correct the tallies.
Part of the computational workload shouldered by Extremem is to track the total allocations performed by each thread along with tracking when previously allocated objects should become eligible for garbage collection. These tallies are reported to standard output.
Nearly all objects allocated by Extremem are eventually supposed to be discarded. At certain critical execution points, the total number and flavors of certain object allocations should equal the total number and flavors of matching object discards. That these numbers do not currently match demonstrates that there are errors in the current calculations of these memory allocation and deallocation tallies.
We need to correct the tallies.