-
-
Notifications
You must be signed in to change notification settings - Fork 670
Minimal runtime GC collects pinned objects. #1646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Seems like none of the memory copying magic, neither the StaticArray needed to break it. A regular Array drops the references to classes anyway. Repro v3: MinimalGCBugReproV3.zip
Bonus: Web Editor reproduction link. Switching to incremental mitigates it. Reproduction overview:
|
1 task
Thanks for digging through this, the repro was super helpful :) Should be fixed with the next release at 0 UTC. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
UPDATE: See the short version of the repro.
However this one might still be useful because it has to pass the test.
Repro: MinimalGCBugRepro.zip
Steps to reproduce:
npm run asbuild:incremental
thennpm test
.123456
.npm run asbuild:minimal
thennpm test
.Reproduction overview:
The text was updated successfully, but these errors were encountered: