trop[bot] 90decd4eaf fix: add missing HandleScope in contentTracing.getTraceBufferUsage() (#50594) ...

The `OnTraceBufferUsageAvailable` callback creates V8 handles via
`Dictionary::CreateEmpty()` before `promise.Resolve()` enters its
`SettleScope` (which provides a `HandleScope`). When the callback
fires asynchronously from a Mojo response (i.e. when a trace session
is active), there is no `HandleScope` on the stack, causing a fatal
V8 error: "Cannot create a handle without a HandleScope".

Add an explicit `v8::HandleScope` at the top of the callback, matching
the pattern used by the other contentTracing APIs which resolve their
promises through `SettleScope` or the static `ResolvePromise` helper.

Made-with: Cursor

Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com>
Co-authored-by: Alexey Kozy <alexey@anysphere.co>

2026-03-31 10:15:13 +02:00

..

app

chore: bump chromium to 146.0.7666.0 (41-x-y) (#49543)

2026-02-17 16:19:16 -05:00

browser

fix: add missing HandleScope in contentTracing.getTraceBufferUsage() (#50594)

2026-03-31 10:15:13 +02:00

common

refactor: improve input handling in FilePath gin converter (#50547)

2026-03-27 22:56:38 +00:00

renderer

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

2026-03-09 23:26:10 +00:00

services/node

feat: enable WASM trap handlers in all Node.js processes (#49839)

2026-02-18 13:22:36 -05:00

utility

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

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