NativeScript iOS Daily: Runtime Startup Crash Fixes
Two merged pull requests close out a class of runtime startup bugs tied to uninitialized or shared state during early launch, with worker threads and script caching identified as the highest-risk area. The runtime version bumps to 9.1.0 following these fixes.
Duration: PT2M11S
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-03T13:14:38Z
- Audio duration: PT2M11S
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 3rd, 2026, and this is NativeScript iOS Daily.
Today's story is about what happens in the narrow window before the runtime finishes starting up — and how that window was quietly causing production crashes.
The headline fix is PR 468, from Eduardo Speroni. Production crash reports showed apps launching several Workers at once hitting an EXC_BAD_ACCESS deep in V8's deserializer, always with a second worker thread nearby. The root cause: script cache reads were served out of a single shared, process-global buffer. When…
The second fix, PR 460 from Adrian Niculescu, addresses a related theme: state that isn't safe before initialization completes. The runtime's isolate pointer was left uninitialized until late in setup, but the destructor and the isolate getter could read it earlier, and the current-runtime pointer is live from…
Both fixes point to the same underlying lesson: multi-threaded, multi-worker startup is where uninitialized or shared state does the most damage, and it's worth auditing for similar patterns elsewhere in runtime initialization.
One incidental note in the same commit: a Jasmine timeout override wasn't actually applying to the new…