You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2022. It is now read-only.
With cfg(debug_assertions) or, since this is extremely expensive, only when a Cargo feature is enabled, we should perform a full collection every time a reference to a GC object is dropped.
This means that objects get freed as soon as the GC would be allowed to, which should expose all possible use-after-free bugs caused either by a bug in rcgc, missing roots, or incorrectly broken/moved object references.
The text was updated successfully, but these errors were encountered:
jonas-schievink
changed the title
Add debug-only checks expose all use-after-frees
Add debug-only checks to expose all use-after-frees
Jan 16, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With
cfg(debug_assertions)
or, since this is extremely expensive, only when a Cargo feature is enabled, we should perform a full collection every time a reference to a GC object is dropped.This means that objects get freed as soon as the GC would be allowed to, which should expose all possible use-after-free bugs caused either by a bug in rcgc, missing roots, or incorrectly broken/moved object references.
The text was updated successfully, but these errors were encountered: