-
Notifications
You must be signed in to change notification settings - Fork 93
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
Disposing contexts #52
Comments
Agree, I would like a mechanism to rush clearing context, perhaps a block
form.
Would you like to work on this?
…On Mon, Feb 13, 2017 at 2:04 PM, koops ***@***.***> wrote:
Maybe I'm missing it, but there doesn't seem to be a way to release a
context and free memory.
This would be very handy given that timeouts can leave the context in an
inconsistent state (finally blocks aren't called, etc.)
Thanks again for your work on miniracer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#52>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAUXS2hJ4JytbTFxCfFo_PMdWh_PKmNks5rcKk6gaJpZM4L_mAu>
.
|
I would like to work on this, yes. But don't wait for me :) |
I just added support for |
Beautiful, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe I'm missing it, but there doesn't seem to be a way to release a context and free memory.
This would be very handy given that timeouts can leave the context in an inconsistent state (
finally
blocks aren't called, etc.)Thanks again for your work on miniracer.
The text was updated successfully, but these errors were encountered: