This article explains why the Roma framework needs a JavaScript engine on HarmonyOS, compares mainstream JS engines, details V8's architecture and JIT pipeline, and provides a step‑by‑step process for cross‑compiling V8 with CMake, GN, Ninja and the HarmonyOS SDK, including code examples and tooling tips.
This article explains the need to adapt the Roma framework for HarmonyOS by selecting and analyzing the V8 JavaScript engine, describes its internal components such as the parser, Ignition interpreter, TurboFan JIT compiler and Orinoco garbage collector, and provides a step‑by‑step guide for cross‑compiling V8 with CMake, GN, Ninja and tool‑chain files to produce a usable library for HarmonyOS native projects.
V8 creates JavaScript closures by lazily parsing functions, using a pre‑parser to detect and record outer‑variable references, copying captured values to the heap, then generating bytecode that builds a function context and closure, ensuring efficient execution while avoiding memory‑leak pitfalls.
This article explains how the V8 JavaScript engine manages memory through stack and heap allocation, describes its generational garbage‑collection architecture—including New Space, Old Space, and various GC algorithms—and offers practical optimization techniques to reduce pause times and improve performance.
This article explains how the V8 JavaScript engine allocates memory, why garbage collection is necessary, describes the memory layout of new and old generations, reviews common GC algorithms such as reference counting, mark‑sweep, mark‑compact and incremental marking, and offers practical tips for writing high‑performance JavaScript code.
This article explains the thread‑merging problem that arises when using PlatformView in Flutter’s multi‑engine setups, analyzes the root causes in both independent and lightweight engines, and presents a comprehensive solution that modifies the engine’s task‑runner merging logic to support one‑to‑many merges.
This article investigates why JavaScript's Object.keys() may return keys in an unexpected order, explains the specification‑defined sorting rules for integer and string properties, demonstrates the issue with timestamp tags on iOS and Android, and explores the actual implementations in QuickJS and V8 engines.
