I have a React-Native project built with Expo that relies on expo-audio / expo-video to stream an 82-minute MP3. Everything works flawlessly while the app is in the foreground, but the moment the device is locked the playback stops at 51.5 seconds and Xcode throws a Signal 9 (SIGKILL). That points to a memory-related crash inside iOS and, from what I can see in Instruments, the heap rises quickly until the OS terminates the process. Scope • The problem appears only on the lock screen; foreground playback is stable. • Goal: identify the root cause (suspected leak / buffer allocation issue inside expo-audio or my configuration) and deliver a code-level fix so the full 82-minute track plays uninterrupted with the phone locked. Deliverables (acceptance criteria) 1. Updated code or config that prevents the SIGKILL and keeps audio playing for the entire 82 minutes on a locked device. 2. Brief explanation of what caused the leak/overflow and how your fix solves it (so I can maintain it). 3. Steps I should follow to reproduce your results in Xcode. Tools you’re free to use include Xcode, Memory Graph, or any Expo Dev Client debugging workflow—whatever gets the job done. If you’ve wrestled with expo-av or similar Core Audio edge cases before, I’d love to get this patched quickly.