fix: template literal crash GC(#2178) - #2295
Merged
dcodeIO merged 1 commit intoJun 9, 2022
Merged
Conversation
2 tasks
Member
|
Referring to #2178 (comment), since marking the |
HerrCai0907
force-pushed
the
fix-template-literals-cause-gc-crash
branch
from
June 9, 2022 09:28
61fa935 to
b5e3e9e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
⯈Another solution to fix template literal bug, see PR #2285
The reason set the color transparent: code cannot get the StaticArray used by template literal, so it is impossible to call __pin / unpin manually, the default transparent is safe.