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
Lands #8764 and #8671.
#8764 keeps WinUI callbacks behind scanned keys, addressing #8734: the
callback pointers that were copied out of the GC-scanned tables into
Reactor element-tree closures, where no scanner could reach or rewrite
them. This is the Windows-side fix, authored on a Windows host.
#8671 completes Node async_hooks lifecycle parity.
Both were showing pr-gate red before #8791 landed, because main itself
was failing `cargo-test` on a Web Streams test.
No version bump.
Co-authored-by: Ralph Küpper <ralph@skelpo.com>
- Fixed WinUI widget, application-exit, and timer callbacks becoming stale after an evacuating garbage collection. Windows Reactor closures now retain stable widget/slot keys and resolve callbacks from GC-scanned storage immediately before invocation; timer callbacks likewise remain in a scanned key-indexed table instead of being copied into opaque `DispatcherTimer` closures.
0 commit comments