NativeScript iOS Daily: Worker Threads Land, Then Get Hardened
A major feature — native worker threads and messaging for the runtime — shipped in PR #454, and it immediately drove two follow-up fixes for real production crashes in how the runtime manages object lifetimes across isolates.
Duration: PT2M17S
Episode overview
This episode is a short developer briefing from NativeScript iOS Daily.
It explains recent repository work in plain language.
- Show: NativeScript iOS Daily
- Published: 2026-08-27T13:17:35Z
- Audio duration: PT2M17S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 27th, 2026, and today's runtime activity is really one story in three parts: new concurrency features, and the lifetime bugs they exposed.
The headline is PR 454: native MessagePort, MessageChannel, BroadcastChannel, and node worker threads, built on top of the DOM exception serialization work in PR 453. This gives NativeScript real EventTarget-based workers and a proper messaging layer, with lazy-loaded globals so apps that don't use workers pay zero…
That assumption is exactly what broke. PR 457, merged this morning, fixes production V8 fatal crashes — the kind of nondeterministic global-handle corruption that only shows up under load on worker isolates. The root cause: a custom finalizer callback contract requires code to either reset or re-arm a handle, and…
PR 456 tackles the sibling problem: Worker JS wrappers were staying alive through "finalizer resurrection" — a pattern where garbage collection condemns a handle while the thread is still running, and disposal logic revives it. That worked by accident, but the team traced it to real heap corruption, because the…
The throughline: shipping cross-isolate concurrency forced a hard look at object…
What's…