Since updating the OS to 26.4, the app has been crashing more often after I launch it.
Please post the full crash log, using the instructions found here.
Additional information: The app was developed using Unity. After contacting Unity, they indicated that based on the crash logs, it is highly likely that a “Segmentation Fault” occurred.
A "Segmentation Fault" just means your app attempted to access invalid memory, which doesn't actually tell you very much about why you actually crashed. The document "Diagnosing memory, thread, and crash issues early" has a good overview of the tools that can help file this sort of issue, followed by some specific examples of what can cause this kind of failure.
I suspect the “Segmentation Fault” is caused by insufficient memory.
No, not really. Memory exceptions (what a seg fault is) happen because you’re accessing memory that you either never allocated or have already freed, neither of which will happen due to direct lack of memory. Keep in mind that your app can't really "run out" of memory in the way you're describing. Your app allocates address space by calling "malloc" and uses real memory when it actually stores data into address space it's allocated. If/when physical memory becomes limited, the system eventually responds by killing your app. That's very different from a segmentation fault.
but is it possible that memory usage has increased significantly in iOS 26.4 compared to previous OS versions?
No, not really.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware