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

Don't clear the context stack in pop #14

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

karlseguin
Copy link
Contributor

Currently, when pop returns, the stack is deinitialized if empty. I assume this is an optimize to free memory ASAP, without having to wait for deinit.

But currently, the only way to free a Ctx is from a callback being executed within pop. You have to call ctx.deinit within ctx.pop, and you possibly have other things to clean up too, like deallocating a heap-allocated Ctx. This makes any operations after @call returns dangerous.

Consider this code:
https://github.com/lightpanda-io/browser/blob/6ae4ed9fc33eb82d7206d52692d8616737d11bf5/src/xhr/xhr.zig#L617

This calls ctx.deinit() within a call to ctx.pop, it then sets the union referencing ctx to null. After that point, the ctx variable/memory should not be used.

Currently, when pop returns, the stack is deinitialized if empty. I assume this
is an optimize to free memory ASAP, without having to wait for deinit.

But currently, the only way to free a Ctx is from a callback being executed
within pop. You have to call `ctx.deinit` within `ctx.pop`, and you possibly
have other things to clean up too, like deallocating a heap-allocated Ctx.
This makes _any_ operations after @call returns dangerous.

Consider this code:
https://github.com/lightpanda-io/browser/blob/6ae4ed9fc33eb82d7206d52692d8616737d11bf5/src/xhr/xhr.zig#L617

This calls ctx.deinit() _within_ a call to ctx.pop, it then sets the union
referencing ctx to null. After that point, the ctx variable/memory should not
be used.
@krichprollsch krichprollsch merged commit 073546a into lightpanda-io:main Mar 4, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants