trop[bot] f4c7a3ff66 fix: prevent use-after-free in PowerMonitor via dangling OS callbacks (#50088) ...

PowerMonitor registered OS-level callbacks (HWND UserData and
WTS/suspend notifications on Windows, shutdown handler and lock-screen
observer on macOS) but never cleaned them up in its destructor. The JS
layer also only held the native object in a closure-local variable,
allowing GC to reclaim it while those registrations still referenced
freed memory.

Retain the native PowerMonitor at module level in power-monitor.ts so
it cannot be garbage-collected. Add DestroyPlatformSpecificMonitors()
to properly tear down OS registrations on destruction: on Windows,
unregister WTS and suspend notifications, clear GWLP_USERDATA, and
destroy the HWND; on macOS, remove the emitter from the global
MacLockMonitor and reset the Browser shutdown handler.

Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>

2026-03-05 17:21:22 -05:00

..

app

refactor: address PathProvider TODO (#49601)

2026-02-02 09:39:20 +01:00

browser

fix: prevent use-after-free in PowerMonitor via dangling OS callbacks (#50088)

2026-03-05 17:21:22 -05:00

common

fix: use proper quoting for exe paths and args on Windows (#50075)

2026-03-05 10:27:40 +01:00

renderer

fix: use setter's creation context when proxying setter in OverrideGlobalPropertyFromIsolatedWorld (#50018)

2026-03-03 10:45:57 +01:00

services/node

fix: revert enabling WASM trap handlers in all Node.js processes (#48976)

2025-11-14 18:57:05 -08:00

utility

fix: broken OOP window.print() on macOS/Linux (#45214)

2025-01-20 10:23:44 +01:00