NativeScript iOS Daily: Worker Startup Cleanup
A single fix addresses workers that fail during startup but don't fully shut down, closing a gap where a broken worker could stay alive indefinitely. The change brings failed-entry-script handling in line with how failed-entry-throw errors are already treated.
Duration: PT1M49S
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-08T13:15:04Z
- Audio duration: PT1M49S
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 8th, 2026, and this is NativeScript iOS Daily.
Today's focus is a single but meaningful fix in worker lifecycle handling, addressed in pull request 473 from Adrian Niculescu.
The core issue: when a worker's entry script doesn't exist, the worker reports the error but doesn't actually terminate. The startup callback returns without shutting things down, so the thread's run loop keeps going, and the underlying thread and isolate stay alive in memory. If the parent process isn't explicitly…
This is notable because NativeScript already handles a similar case correctly — when a worker's entry script throws an exception during startup, it terminates itself right away. PR 473 brings the missing-script case into alignment with that existing behavior, so both failure modes now clean up consistently.
For developers, the practical impact is about reliability and resource management. Silent zombie workers are the kind of bug that doesn't show up in a quick test, but can quietly leak memory or threads in longer-running apps, especially in code paths that spin up workers speculatively or based on user-provided…
The changes touch runtime worker and worker wrapper code,…
Nearby episodes from NativeScript iOS Daily
- Worker Overhaul and a Suspended-App Crash Fix
- Worker API Gets a Redesign, Plus a Suspend-State Crash Fix
- Runtime Startup Crash Fixes
- Closing the Worker Memory-Corruption Hunt
- Worker Threads Land, Then Get Hardened
- Web Globals Land, Memory Leaks Get Squashed
- The Runtime Goes Web-Standard
- Loader Hardening Closes Out