Hi Kevin, We have now filed FB25422068, following your request for an iOS 18 bug report. The JSC/WebKit crash pattern is still occurring on iPhone XR (iPhone11,8) running iOS 18.7.11 (22H384). We have two production incidents from different devices. Both crash on the main thread while initializing WKWebViewConfiguration, before subsequent WKWebView construction or URL/page loading. Using UUID-matched system libraries, we confirmed the immediate failure: pthread_create returns EAGAIN (35) while starting the JSC scavenger thread, triggering the assertion at pas_scavenger_notify_eligibility_if_needed +348 (EXC_BREAKPOINT/SIGTRAP). The feedback includes sanitized crash excerpts and disassembly evidence. Together with the earlier iOS 18.7.10 (22H374) report in this thread, this raises concern that the iOS 18 branch may still be affected by the Structure Heap reservation / VM-accounting issue. Our evidence is consistent with that explanation, but does not conclusively establish the same underlying resource-exhaustion cause; we do not yet have an incident-time VM map or deterministic local reproduction. Could Apple please confirm: Does iOS 18.7.11 (22H384) include the fixes for r.177567438 / WebKit Bug 315240 and the related r.174732430 VM-accounting issue? If the required fixes are missing, is a backport to the iOS 18 branch planned, and can you share the target update or timeframe when available? This matters for devices such as iPhone XR that cannot upgrade to iOS 26. What supported mitigation is recommended in the meantime, and is Extended Virtual Addressing appropriate for these devices? Thank you.