@evertonmdz
I've already tried this fix when it was posted earlier, did not help at all. So far every fix posted in this thread (including the ones I posted), have turned out to be useless. The bug is very random and doesn't always occur, so it can seem like every random workaround 'fixes' it, but it will inevitably happen again ☹️
I understand, however in my case solved for real! stopped the leak and fall of Fps generated by it, try to put the maximum amount of memory that appears as "recommendable"! minimum 400 and leave!
in my case was thus: http://img29.imageshack.us/img29/1223/7cu3.png
remembering that my memory is 8GB!
That is not a fix, that just delays the inevitable and also beats the crap out of your hard drive in the process. I was doing that but after one of my drives decided to choke to death I decided it was better to just let the game crash when I run out of RAM rather than use a page file.
I've gone entire days without it happening, but it still happens eventually and sometimes more often.
@evertonmdz
I have pretty much the same PF settings (mines set to 4096mb), and I have 16 gigs of ram. I still get this leak. I don't see why pagefile settings would have any effect on a memory leak. The pagefile is only used once the system has run out of memory.
actually Battlefield 4 uses a lot of virtual memory, so you do not know, but uses!
Actually Battlefield only uses virtual memory as an emergency when it runs out of system memory (RAM).
It shouldn't use VM at all as it's slower and less reliable than RAM when running a program. RAM is there for a reason, I have 16GB of RAM and I have disabled my VM for testing. The leak still occurs with or without VM.
Setting your PF to your SSD will just shorten it's life immesurably especially with this kind of memory leak that is write intensive. DO NOT set your PF to your SSD.
