Potential memory leak in STExtractionservice on iPhone 17 Pro Max with iOS 26
I recently had to take back my newly bought iPhone 17 Max Pro after bug_type_298 killed the backboardd process leading to an undervolt error to the processor. I was left with a apple logo loop of doom issue that couldn't be fixed and I got a refund due to lack of stock.
I bought a new one today (with a lot of luck) and checking the analytics after setting it up as a new phone (to avoid transfering a bug from pervious back ups) and I found another Jetsam event (literally 15m into setting it up) saying it had to shutdown a backboardd - the exact issue that bricked my first one. Backboardd is a critical process in the function of the phone (to my understanding at the kernel level) so to have it be jettisoned is not a good thing!
I noticed in the logs that the STExtraction logs occured at the same time as the Jetsam logs so having a look into it I discovered what could likely be causing the issue with memory that lead to the death of my first phone and apple needs to patch this immediately. (log dump below)
The core issue is a runaway system process in iOS 26 (STExtractionService/nsurlsessiond) that has a bug causing it to exceed resource limits and generate a massive I/O load. This load spikes the RAM, forcing the crash of a critical system process which eventually led to the death of my first phone. I'm now worried this will kill my second phone. To be frank I likely wont buy another one if I have to take this one back until this is fixed!!
I have reduced the load on my ram by turning on reduced motion, limiting the screen to 60 fps turning off background activities for apps and turning off adaptive monitoring for the battery.
"app_name":"STExtractionService","timestamp":"2025-09-30 17:13:51.00 +0800","app_version":"1.0","slice_uuid":"D566AF36-534C-3C85-BECF-E0BBFE440E69","build_version":"1","bundleID":"com.apple.STExtractionService","duration_ms":"728427","share_with_app_devs":1,"is_first_party":0,"bug_type":"145","os_version":"iPhone OS 26.0.1 (23A355)","roots_installed":0,"name":"STExtractionService","incident_id":"3741D217-788A-4BA2-B82F-6799D936F75B"}
Date/Time: 2025-09-30 17:00:44.487 +0800
End time: 2025-09-30 17:12:52.914 +0800
OS Version: iPhone OS 26.0.1 (Build 23A355)
Architecture: arm64e
Report Version: 66
Incident Identifier: 3741D217-788A-4BA2-B82F-6799D936F75B
Share With Devs: Yes
Data Source: Microstackshots
Shared Cache: 4C4CAEE6-F334-3B74-B7F2-FA7C4316C1F9 slid base address 0x18fe88000, slide 0xfe88000
Command: STExtractionService
Path: /System/Library/PrivateFrameworks/StreamingExtractor.framework/XPCServices/STExtractionService.xpc/STExtractionService
Identifier: com.apple.STExtractionService
Version: 1.0 (1)
Resource Coalition: "com.apple.nsurlsessiond"(269)
On Behalf Of: 76 samples nsurlsessiond [172] (76 samples originated by nsurlsessiond [172])
Architecture: arm64
Parent: launchd [1]
PID: 362
Event: disk writes
Action taken: none
Writes: 1073.97 MB of file backed memory dirtied over 728 seconds (1474.37 KB per second average), exceeding limit of 12.43 KB per second over 86400 seconds
Writes limit: 1073.74 MB
Limit duration: 86400s
Writes caused: 1073.97 MB
Writes duration: 728s
Duration: 728.43s
Duration Sampled: 721.92s (event starts 6.21s before samples, event ends 0.30s after samples)
Steps: 796 (10.49 MB/step)
Hardware model: iPhone18,2
Active cpus: 6
Memory size: 11.42 GB
HW page size: 16384
VM page size: 16384
Shared cache residency: 27.89% (1549.86 MB / 5556.75 MB)
Advisory levels: Battery -> 2, User -> 3, ThermalPressure -> 0, Combined -> 2
Free disk space: 922.17 GB/953.08 GB, low space threshold 150 MB
Vnodes Available: 72.07% (20180/28000, 14000 allocated, 14000 soft limit)
Models: none
[Re-Titled by Moderator]
Original Title: iPhone 17 Pro Max and iOS may have a major memory leak at the kernel level.
