I think there is a serious misconception out there that gameconfig mods are magic "one size fits all" bullets that will allow any combination and any quantity of mods on any system - all running in perfect harmony for hours on end. Not in my experience.
First gameconfig.xml is not a modder's invention. It's a GTA5 file found in the game's common and update folders. Modders like F7YO and others do their best to tweak and fine tune this file - of course they do it on their own systems and as they say "results will vary".
There are so many combinations of hardware, software, and mods - how would it be possible to satisfy all users.
I'm using F7YO's previous version of the gameconfig because the new one doesn't work for me. How long does it take me to crash on my rig with the previous version? Well with one or two or 3 vehicle addons and the same number of addon peds, with RCA and Forests mods I can play for hours without crashing.
If I spawn say 20 peds or 10 high polygon cars and even delete them in C# so that the models are no longer recognized, I'll crash in 5 to 30 minutes depending on which mods I've spawned. First I will notice a drop from 60FPS to 30 FPS, then I'll notice texture dropouts and finally it will just hang, game over.
All that to say, it's better to try to manage your own game rather than expect a gameconfig mod perfectly suited for your rig and your mod set.
There are many ways to mitigate crashing. Combine your packs, reduce your packs, temporarily disable some of your mods, or just be more selective as to what you install and keep.
Game designers have a helluva challenge to manage memory allocation to different components of games with team members advocating for their fair share, and these memory constraints do not take into account modding, in fact R* unlike Valve with l4d, hl, CS, TF, etc. encouraged the community to mod and create their own levels, even supplying and supporting tools for that purpose. R* only care about their IP and online users.
