NativeScript iOS Daily: Worker Threads Land, Isolate Safety Hardened

The runtime gains real worker threads with message passing and serializable exceptions, alongside two separate fixes for isolate and lifetime safety bugs found during that work. tvOS also moves onto the current V8 and NativeScript toolchain.

Duration: PT2M21S

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-09-12T13:13:43Z
  • Audio duration: PT2M21S

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 September 12th, 2026, and this is NativeScript iOS Daily.

The headline: worker threads are now real in the iOS runtime, and getting there surfaced two serious concurrency bugs that are now fixed.

Eduardo Speroni's PR 454 is the centerpiece — native Message Port, Message Channel, Broadcast Channel, and node worker threads support, all as lazy globals so there's no boot cost if you don't use them. It builds on PR 453, which makes DOM Exception properly serializable so it survives structured clone and post…

But shipping real threads exposed real bugs. PR 456 fixes a heap corruption issue where worker JS wrappers relied on finalizer resurrection — the garbage collector would condemn a wrapper mid-thread, then a custom patch would revive it, and that interplay could leave dangling memory that crashed the concurrent…

The second bug, in PR 475, is related but distinct: Objective-C callbacks into JS could pass an isolate-liveness check, then get granted a lock only after the runtime had already cleared its caches during teardown, continuing with a dummy, disposed cache. The fix re-checks liveness after the lock is held, not just…

The common thread across 454, 456, and 475:…

Nearby episodes from NativeScript iOS Daily

  1. Worker Startup Lifecycle Fixes
  2. tvOS Gets a Runtime Overhaul
  3. Worker Startup Cleanup
  4. Worker Overhaul and a Suspended-App Crash Fix
  5. Worker API Gets a Redesign, Plus a Suspend-State Crash Fix
  6. Runtime Startup Crash Fixes
  7. Closing the Worker Memory-Corruption Hunt
  8. Worker Threads Land, Then Get Hardened