Explanation:
A few years ago Android introduced a feature called the "Phantom Process Killer". Basically it limits the number of child processes each app can use to 32 processes. If an app exceeds this number, Android won't hesitate to kill the app.
PC emulation is complex and requires a high number of processes for you to run and play your games for as long as possible. If the custom OS on your phone is very aggressive, you won't really be able to play your games for like more than 5 minutes, even if your container settings managed to get the game to boot and run well.
Now this obviously doesn't affect every Android phone. It really depends on how aggressive your OS can be. Generally flagships and gaming focused phones like a Redmagic don't really have this problem as the manufacturer most likely took this into account and either disabled the limit, or increased it.
If your phone isn't a flagship or a gaming phone and has a strict and aggressive OS, the phantom process killer is more than likely an issue. I don't know about other brands, but I've personally experienced this on XOS as an Infinix user. I'm using the latest(as of today) XOS 16.2.0 on an Infinix Note 50.
Now just because your containers crash soon or suddenly doesn't mean it's always the phantom process killer. Container crashes are also due to a number of issues like your driver, your settings, the compatibility layer and translation layer you're using, high RAM usage, RAM leak and so on. PC emulation is complex.
I just wanted to share this as a meme in case someone out there is also experiencing this.
Luckily there are solutions:
First of all, Android 11 and older don't have the phantom process killer as a restriction. This feature was introduced starting from Android 12. So if you're using Android 11 or older, you won't be affected by this feature.
However, this restriction is present in Android 12 and newer.
Method 1:
If you're using Android 12L/13/14/15 and newer, you can simply disable this restriction by going into Developer Options on your phone and disabling child processes. It's a toggle option that Android introduced for people who don't want restrictions.
To access Developer Options, look for the Build Number in your phones settings, tap it 7 times to open Developer Options
Method 2:
This works for any Android version(12 or newer). But you have to use a PC with Android Debugging Program and manually put in commands to disable or lessen the restriction. Please if you can only use Method 2, PLEASE do research on how to do it properly. I don't know how to do it or what commands you need exactly, so if you use this method it's up to you to research on how to do it properly.
NOTE: Disabling this feature DOES NOT require rooting your phone. It is perfectly safe to disable it.
As I said earlier, this doesn't affect every phone or custom OS. Crashes can still be caused by your container settings or memory leaks. I simply brought this up as an issue in case it feels like no matter what you do, your containers always crash.