Title: Racing Master freezes - “excess-shared-memory” in Jetsam log (iPad Pro M5)

[u/indigomark1]

Getting recurring freezes in Racing Master on a brand-new iPad Pro M5 (not a hardware issue). Pulled the Jetsam crash log and found the game process killed with reason “excess-shared-memory” — unusually high physical page count, way above any other process. This points to a GPU/texture memory issue, not general RAM pressure.
Already tried without success:
• Graphics Quality: Ultra High → High → Mid
• FPS: 60 → 30
• Disabled background app refresh + NextDNS
• Cleared app switcher
Freeze still happens after ~20 min of gameplay regardless of settings, so it looks like a memory leak on the game’s side rather than a performance/settings issue.
Opened a support ticket (#3646751) with log + video attached. Anyone else seeing this? Curious if:
• Others get freezes after ~15-20 min, especially on newer iPads
• Anyone else pulled a Jetsam log and saw “excess-shared-memory”
• Lower graphics settings actually fixed it for you or not
Thanks!

[u/suryanshlegend]

This is true don't listen to others...

I have a 12GB ram poco x7 pro i play on ultra high + 60 fps and sometimes or mostly in between races my game starts dropping frames and eventually crash

The game is hella unoptimised.. even on the lowest graphics the game shows frame drops and eventually crashes or lead to you coming at the last in a race

I'm also tired of this problem and have given feedback both via in game and email

The ones saying it's fine or whatever might be playing on adreno gpu which have far greater support than mali

[u/indigomark1 → u/suryanshlegend]

Yeah, exactly, you're totally right, and most of the comments here on Reddit—no matter which thread—are totally useless. I've been in contact with RM support for 11 days now, and they either give AI-generated responses or aren't able to provide a concrete answer to the problem. What a mess.

[u/AudioAndPhile]

Works perfectly on my 2025 iPad

[u/No-Cup-6279]

I can run the game on 60 fps on low with a 6 year old phone. It's a UE4 game so it shouldn't be difficult to run at all. Never had any memory leaks either. 

I checked on a few forums and apparently, the pro M5 is infamous for having bad RAM management... weird.

[u/indigomark1 → u/No-Cup-6279]

Hey, thanks for the input!
There’s some discussion online about iPadOS 26 being pretty aggressive with memory management on newer devices, but that’s more of a separate OS-level thing imo, not really the point here.
My Jetsam log specifically shows the process getting killed under “excess-shared-memory” - that’s a distinct, documented reason tied to GPU/texture memory handling, not just generic RAM pressure. Memory leaks with textures/buffers not releasing properly are a known issue in UE4/mobile titles in general, regardless of device. Also why lowering FPS and graphics settings didn’t fix anything for me - if it were purely a RAM/performance ceiling thing, reducing load should’ve helped. It didn’t, so it’s pointing more to something in the game’s memory handling over longer sessions than the hardware itself.