trop[bot] d2841683c1 fix: crash calling OSR shared texture release() after texture GC'd (#50500) ...

The weak persistent tracking the OffscreenReleaseHolderMonitor was tied
to the texture object, but the release() closure holds a raw pointer to
the monitor via its v8::External data. If JS retained texture.release
while dropping the texture itself, the monitor would be freed on GC and
a later release() call would crash.

Track the release function instead of the texture object. Since the
texture holds release as a property, this keeps the monitor alive as
long as either is reachable.

Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com>
Co-authored-by: Sam Attard <sattard@anthropic.com>

2026-03-26 00:50:00 -07:00

..

app

refactor: address PathProvider TODO (#49601)

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

browser

fix: read nodeIntegrationInWorker from per-frame WebPreferences (#50122) (#50467)

2026-03-24 22:48:27 +00:00

common

fix: crash calling OSR shared texture release() after texture GC'd (#50500)

2026-03-26 00:50:00 -07:00

renderer

fix: read nodeIntegrationInWorker from per-frame WebPreferences (#50122) (#50467)

2026-03-24 22:48:27 +00: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