Commit size, why is it so high?

I've noticed that, on the rare occasion I play BeamNG anymore, that I need to close absolutely everything sometimes including driver software just to load into a level. Upon further investigation (and multiple hard locks of my PC caused by BeamNG), I noticed that it requests up to 4x more memory than it uses.

Why are commit sizes using up to 40% of my RAM (16GB), that's over 6 GB, when the game never exceeds 3GB of memory in these cases. Even when it does, the commit size increases as well.

Also, When I spawn more vehicles, the commit size just increases, as does used memory.

So I must ask, why are the commit sizes so massive in the vanilla game? It's a problem that has made the game nearly unplayable for quite a while now.

 

When I had 8GB of ram, only times I had to close something was when playing Bob's Tennessee map as that map pushes all limits of BeamNG it does require quite bit of memory from computer.

With 16GB I don't need to close anything, I can have two browsers open with hundreds of tabs taking more than 2GB of ram, I can still spawn as many vehicles as my i7 CPU allows and I don't get to 16GB commit, or any other issues.

Quite often I have OBS loaded for recording too and CoolSoft's virtual midi synth with Salamander piano takes yet another gigabyte of memory.

This leads me to thinking that maybe there are something else than committed memory causing issues that you are experiencing?

I have not experienced any lockups in BeamNG, usually lockups point towards cooling issues or malfunctioning hardware.

Have you ran memtest, what are your GPU and CPU temps during gaming session? I use MSI Afterburner to monitor temperatures while in game.

You could try to exclude cpu heat issues with Intel burn test, it loads cpu heavily and if pc is not locking up no matter how you run that, then cpu heating issues are excluded:
http://www.majorgeeks.com/files/details/intelburntest.html


I had some issues with current computer initially, but bios upgrade fixed issue with XMP settings and I set voltages to manual instead of auto, as it seems motherboard liked to run memory at higher voltage which did cause bit of instability issues.

Maybe you could list everything you shut down when playing BeamNG, perhaps there is possibility of some conflict with some other software that some members might have information about?

Certainly there must be something that causes those issues for you, sometimes finding can be bit of work though, but while writing this, I have over 1GB memory use from two browsers, ton of other stuff and Tennessee map loaded in BeamNG.Drive which has committed 9GB of ram while using bit over 4GB and no issues, so for me it sounds like that committed memory is not the main cause of the issues, hopefully we can find the issue and you can enjoy from BeamNG again!

 

I have no page file. When something decides to reserve all remaining memory, my PC calls it quits (hard lock, or other symptom).

No heat issues here, luckily have never had any. I have 16GB of RAM as well, but my only guess is that we're on different OSes. I run Windows 7, which seems to be heavy on memory as is. That, combined with drivers and services, has a large memory footprint on it's own (~20-25%)

If I top that with a browser, Discord, Skype, and Blender/Visual Studio, then BeamNG pushes that too far.

 

I have two visual studios, but no Skype or Discord and I'm running Win8 that has customized to work as WinXP more or less, I'm too old to learn modern

Does enabling page file stop this problematic BeamNG behavior?

I have had no page file and page file, not much difference there really, some other software complains about memory without page file even memory usage is not even near maximum, so I turned it on. I have NVME SSD, so I guess it shortens life a bit.

 

Radio silence here? It's getting very tiring having things crash on me when I should have multiple GB of memory left (that BeamNG reserves and never uses) :/. Especially when modding since every reload seems to just increase the commit size endlessly.

 

I have never noticed this problem, but then again I have a pretty insane machine. When I go home tonight I will fire up my rig and see how much memory gets used. I have 32GB available at the moment so that should be plenty to just start chucking stuff at it and seeing what sticks.

 

One thing worth to test might be trying with swap file on and off, because I have 16GB and have not been able to run this issue, but I have swap file on, where as Dummiesman has it turned off.

When I had 8GB and swap file turned off, I got some crashes with BeamNG which were something bit like this, with Win8 I got warning to close off programs to prevent problems, not sure if that comes with Win7.

Oh yes and page file is same as swap file in my head.

 

Got this on x86. Definitely more manageable.
View attachment 238182

EDIT: Seems it still wants to use a lot. Just hit the x86 limit while playing around on JRI
1.295GB used. 3.710GB commit

 

Running with one was killing my hard drive and performance. Made my PC very sluggish with almost nothing running.

(Also it's worth noting that since this topic I've had a fresh install of Windows 7, and the issue still persists)

 

Huh while commit size is big it doesn't affect my current PC performance at all, and wasn't affecting my old PC with 8GB of DDR3s too. Take a look, game is maxxxed out (only Updates per face at 2nd lowest as it's really smooth don't need to make it higher) in 1080p on JRI.

Using only 1,5GB, commit was atm 3,3GB - seems reasonable

ok now with 16 cars it uses around 3,3GB but commit is around 7,4GB - high but still available 10,6GB out of 16GB and I was able to smoothly run explorer and navigate through forums, windows worked just fine, run other apps etc.

It crashed after spawning 21st car until then everything was working ok, even in game UI wasn't lagging too much - commit ~8GB using ~3,5GB (when it crashed system alone used 1,7GB)

Alrighty then, let's try The Witcher 3! - all on UBER totally maxed out:

And what do we see 2,4GB used 5,4GB commit - so it commits 2,25 times more than it uses, well look BeamNG does EXACTLY the same.
GB commited / used on BeamNG example:
3,3 / 1,5 = 2,2
7,4 / 3,3 = 2,(24)
8 / 3,5 = 2,29

I didn't had problems on windows 7 on my old PC, didn't had problems on windows 10 on old PC, didn't have any problems on windows 10 with current PC, my friends don't experience any problems like you and seems like other peoples on forums don't have that problems too. Belive me I checked it before when you talked about it (on my PC win10, laptop win10 and friend's PC win7) just for my own information, everything was ok and I write this post just as evidence.

 

Interesting... I didn't seem to have any problems with this either... although Beam did use a large amount of memory.

Computer at idle.


Start the game and threw in a car.


Added 6 more for 7 cars.


Drove it around some.


After some time. (and a wreck)


Just started adding cars (was at 12 here)


Kept adding more all while watching the ram and at 16 (where my game crashed) I was at 9.8Gbs of ram used... while still a lot... with 16Gbs I wouldn't think you would be having any problems, but I don't claim to know anything, I am just posting what happened to me.