Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Start thinking in an incremental GC during a VM dojo
Entry point of the GC in the VM is in SpurMemoryManager>>sufficientSpaceAfterGC:
We added a call to incrementalFullGC and finishIncrementalFullGCWithoutInterruption
Then, we duplicated the GC logic into these two submethods
Note: we must change SpurMemoryManager>>fullGC primitive that is called from the image side
So far we only tried to let the VM execute Pharo code in between the different steps of the mark phase.
VM compilation is ok but there are VM crashes probably because:
should we always mark newly allocated objects when the incremental GC is running
...
Unit test to write: