Tri Color GC Implementation #54
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonasongg
approved these changes
Nov 4, 2025
There was a problem hiding this comment.
LGTM! the logic looks correct to my limited understanding of a tricolour GC (correct me if I'm wrong!)
- if write barrier is triggered, move the white object to grey (save to be greyed)
- if memory is full, trigger GC (depending on flag, trigger tricolour vs pre-existing GC)
- otherwise, concurrently run tricolour GC
- Initiate: collect roots and mark grey
- Mark: pop from grey, mark its children as grey
- Mark: mark objects from save_stack as grey
- Sweep: once grey is empty, free white objects, and make black objects white for next cycle
great that you've added a profiler as well to measure GC performance :)
| } | ||
|
|
||
| list() { | ||
| if (this.addr >= 256) console.log(this) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.