Ensure Generator::State is kept on the stack
#930
Merged
+6
−1
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.
Fix: #929
I don't know how it's possible, butsomehow theselfreference is optimized out of the stack. Perhaps because we inline so aggressively that the compiler end up spilling it on the heap.Actually I get it now, the actual caller is:
So the GCed variable is
VStatewhich indeed is no longer reachable rather quickly. So the fix does checks out.Repro:
But in practice the cause was just that the issued warning calls Hash#inspect on a big hash, which triggers GC.
So it can be triggered even more reliably with: