#v8

Originally published at norvik.tech Introduction In-depth analysis of the recent Chrome...

How to fix CVE-2026-85046: upgrade Chrome to 152.0.7977.82 (Linux) or 152.0.7977.82/.83 (Windows and Mac)

A Hacker News headline turned a contained V8 type-confusion bug into 'sandbox RCE in all Chromium versions.' The real story is more interesting: how Chromium's defense-in-depth actually held, why V8 keeps producing this exact bug class, and what the coverage got backwards in both directions.

See how Cloudflare's AI agent runtime uses V8 isolates and containers on demand, with a cost model and escalation checklist for multi-agent engineering teams.

Introduction: The Allure of the Nova Proto NP01 There’s something about Samuele "Sammy"...

CVE-2026-3909 and CVE-2026-3910 put 3.5 billion Chrome users at risk. This is a 2026 roundup of the Skia and V8 attack surface — what the vulnerabilities are, why browser engine bugs are hard to kill, and what defenses actually reduce exposure.

How V8's generational garbage collector works, why high allocation rate causes jank, and practical strategies to reduce GC pressure in frontend code.

How the ECMAScript specification forces V8 to leak whether DevTools or any CDP-enabled tool is...

You upgrade your AI agent framework. You run gateway start. Seven seconds later, it's dead. No error...

Separate ECMAScript guarantees from V8 optimizations, then inspect holes, packed storage, elements kinds, sparse dictionaries, and TypedArrays.

A clear guide to how garbage collection works in Node.js, powered by the V8 engine. Learn the processes, phases, and useful tips for memory management.

V8 pointer compression finally lands in Node.js: one Docker image swap cuts heap memory ~50%, improves P99 latency, and can save $80K-$300K a year.