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 treat freeing in a destroyed context as an error #333

Closed
eyalroz opened this issue May 25, 2022 · 0 comments
Closed

Don't treat freeing in a destroyed context as an error #333

eyalroz opened this issue May 25, 2022 · 0 comments

Comments

@eyalroz
Copy link
Owner

eyalroz commented May 25, 2022

It should not be an error to free a pointer when its context has been destroyed. That's like double-free'ing, which should be ok. It might be warning-worthy, or perhaps an error in a strict sense, but no more than that. Especially since we don't increase the primary context reference count with allocations.

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

No branches or pull requests

1 participant