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.
There's nothing wrong with having the page file on your SSD. Modern SSD's can hold up to a ton of writes and last years and years. SSD's rarely fail do to running out of writes unless you are constantly abusing it with unusual write heavy workloads. Obviously an application leaking memory like this is an unusual scenerio.
@bwat47 wrote:There's nothing wrong with having the page file on your SSD. Modern SSD's can hold up to a ton of writes and last years and years. SSD's rarely fail do to running out of writes unless you are constantly abusing it with unusual write heavy workloads. Obviously an application leaking memory like this is an unusual scenerio.
Which is why I stated to NOT set the Pagefile to the SSD. This scenario causes an extraordinary number of writes (reads are irrelevant) to the SSD which in turn shortens it's life. Not something that people will want IMO.
If you want a memory leak using up your SSD be my guest, this is not normal operation by any means. People who can afford SSD's generally have plenty of RAM and have no need for a page file unless you need complete memory dumps on system failures.
