Does V8’s Isolate::TerminateExecution cancel pending timers and promise reactions?

Direct Answer

Isolate::TerminateExecution cancels pending promise reactions (microtasks) but does not cancel pending timers. Because timers are managed by the host environment's event loop and not by the V8 engine itself, V8 has no mechanism to reach into the host's scheduler to revoke them.

Behavioral Breakdown

Promise Reactions (Microtasks)

When TerminateExecution is invoked, V8 halts the current execution and clears the internal microtask queue. Any promise reactions that were queued but not yet executed are discarded. This ensures that the immediate chain of asynchronous JavaScript execution is severed.

Timers (setTimeout/setInterval)

Timers are host-side constructs. Whether you are using Node.js (libuv) or a custom C++ embedder, the timer is a record in the host's memory that triggers a call back into V8 at a later time. TerminateExecution only affects the internal state of the Isolate; it does not communicate with the host's event loop. Consequently, these timers remain active and will attempt to fire as scheduled.

Implementation Requirements for Hosts

To fully abort all work associated with a script, the host must implement a manual cleanup strategy. Relying solely on V8's termination will lead to resource leaks or runtime errors when a stale timer attempts to execute in a terminated Isolate.

1. Track Timer Handles: Maintain a registry of all active timer IDs associated with the specific execution context.
2. Manual Cancellation: Call the host-specific cancellation function (e.g., clearTimeout or the equivalent C++ API) for every tracked handle immediately after calling TerminateExecution.
3. Handle TerminateException: Be prepared for the Isolate to throw a TerminateException if you attempt to execute further code before the termination state is fully cleared or handled.

Assumptions and Verification

This behavior is consistent across modern V8 versions where the microtask queue is managed internally. However, if your host implements a custom microtask loop outside of V8's standard PerformMicrotaskCheckpoint, you must verify if your custom loop is also being cleared.

Verification Step: To confirm this in your environment, schedule a setTimeout and a Promise.resolve().then(). Invoke TerminateExecution and observe that the promise callback never fires, while the timer callback still attempts to enter the Isolate.