trop[bot] b5c7b6fddd fix: prevent GBytes leak in GdkPixbufFromSkBitmap on Linux/GTK (#49895) ...

Inside gtk_util::GdkPixbufFromSkBitmap, g_bytes_new() was called
inline as an argument to gdk_pixbuf_new_from_bytes(), which per
GTK docs does not take ownership of the GBytes - it adds its own
internal reference. The caller's GBytes* was never stored or
unreffed, leaking 4 x width x height bytes of pixel data on every
call.

Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com>
Co-authored-by: redeemer <marcin.probola@gmail.com>

2026-02-20 14:58:05 -08:00

..

app

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

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

browser

fix: prevent GBytes leak in GdkPixbufFromSkBitmap on Linux/GTK (#49895)

2026-02-20 14:58:05 -08:00

common

chore: bump chromium to 146.0.7680.16 (41-x-y) (#49838)

2026-02-20 14:30:11 -05:00

renderer

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

2026-02-18 13:22:36 -05: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