NativeScript iOS Daily: Web Globals Land, Memory Leaks Get Squashed
The runtime shipped its lazy-global architecture with TextEncoder, DOMException, and CustomEvent, while a parallel wave of fixes closed out native memory leaks across the interop layer. Together they mark a maturing runtime: new spec-compliant web APIs going in clean, and old ownership bugs going out.
Duration: PT2M28S
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-26T13:14:20Z
- Audio duration: PT2M28S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good evening, it's August 26th, 2026.
Tonight's story is really two stories that reinforce each other: the runtime is opening its doors to more web-standard globals, and at the same time it's closing the door on a long tail of memory leaks in the native bridge.
Start with the globals work. PR 448 introduced the lazy-global tier — a mechanism that registers builtins like TextEncoder, TextDecoder, atob, and btoa on the global template without compiling or allocating anything until first use. That's the foundation, and it paid off immediately: PR 452 built DOMException and…
The second theme is cleanup in the interop layer, and it's a long list for a reason: these are the kinds of leaks that only show up under load. Commit 8080bc0 alone fixes six distinct issues — a leaked log string, a stranded block copy when passing JS functions as Objective-C blocks, a rebuilt trampoline on every…
One infrastructure note: commit 269e626 fixes Xcode's build phase to resolve Node through a committed environment file, so version-manager installs of Node no longer break local builds.
What to remember: if you're adding native-facing globals, build on the lazy tier — don't hand-roll another eager global.…