Hi Kevin, Following up on your note that this issue should be fixed in iPadOS 26.6 beta 5 or later, could you confirm whether the same fix was backported to iOS/iPadOS 18.7.10? We are seeing what appears to be the same virtual address space exhaustion on an iPhone XR running iOS 18.7.10 (22H374). Our app needs to instantiate WKWebView. In VM Tracker, WebKit initialization results in a large virtual address reservation attributed to: mach_vm_map JSC::StructureMemoryManager::StructureMemoryManager() JSC::initialize() WebKit::InitializeWebKit2() -[WKWebViewConfiguration init] -[WKWebView initWithFrame:] The initial reservation request shown by Instruments is 2 GB, and the successfully reserved Structure Heap region appears to be approximately 1 GB. Later, malloc/operator new starts returning NULL for allocations as small as a few hundred bytes, even though the app's physical footprint is below 1 GB and os_proc_available_memory() still reports approximately 900 MiB available. This is not a jetsam termination, and the failing allocation occurs at different call sites. We also performed a controlled entitlement comparison using the same device, application configuration, and workload: With only Increased Memory Limit enabled, allocation failed at approximately 859 MB. With only Extended Virtual Addressing enabled, the app reached approximately 1.17 GB. This seems consistent with virtual address space exhaustion rather than physical memory pressure. I understand that iOS 18.7.10 and iOS 26.6.1 were both released on August 17, 2026, but they are maintained on different branches. Could you please confirm: Does iOS 18.7.10 contain the fix for rdar://177567438 / WebKit Bug 315240? If not, is a backport to the iOS 18 branch planned? For devices such as iPhone XR that cannot update to iOS 26, is the Extended Virtual Addressing entitlement the recommended workaround? WebKit Bug 315240: https://bugs.webkit.org/show_bug.cgi?id=315240 Thanks.

This problem has been fixed in macos 14.3

ensureEmulatedControllerWithDevice It seems that this is caused by the mac's emulation controller, can I do anything to fix ti?