Skip to content
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

Fully investigate GC issues #2

Open
brian-armstrong opened this issue Mar 11, 2016 · 3 comments
Open

Fully investigate GC issues #2

brian-armstrong opened this issue Mar 11, 2016 · 3 comments

Comments

@brian-armstrong
Copy link
Member

It seems that right now Firefox GC is likely collecting the receiver some short time after it is created. This is a regression. I'd like to fully solve these sorts of issues once and for all.

@lastmjs
Copy link

lastmjs commented Oct 28, 2017

I imagine compiling to wasm might fix this and all other gc issues, since the wasm VM doesn't even support GC yet.

@lastmjs
Copy link

lastmjs commented Oct 28, 2017

And wasm has it's own VM designed for non-GC languages like C/C++, so your compiled code isn't running in a GC VM at all once compiled to wasm.

@brian-armstrong
Copy link
Member Author

wasm would definitely be a better fit. I'm not sure it was really an option when I put this together.

It's worth noting that the GC pause issue I'm seeing here may just be WebAudio pausing and not quiet.js, not sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants