Fix GC: don't increment megablock count, when re-use the megablock in free list #32
Conversation
This file contains 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
|
Is the BUG duplicated with _JHC_JGC_NAIVEGC compile flag? |
master-q
added a commit
that referenced
this pull request
Aug 13, 2013
Fix GC: don't increment megablock count, when re-use the megablock in free list I'm confused. It's a BUG of my code. Merged.
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.
The problem is caused, when
_JHC_JGC_LIMITED_NUM_MEGABLOCKis enabled.The heavy-memory-use program call
s_new_megablockvias_alloc. Becauses_new_megablockhas free list, this does'nt always cause a lack of memory.But
s_new_megablockis increment mega block count on each call. So, we reach to limit before a lack of memory.