Memory Leak
- Thread starter Toekiller
- Start date
The minimum memory any VR player should have as advised by frontier is 16GB of ram. So the initial pagefile you have should be 16gb with maximum set to 48gb. So I guess you should also check you have at least 50GB free HDD space.
Is there any more news or progress on this matter as its getting ridiculous now every 5 mins memory creeps up and freezes
Starting to be impossible to play
I5 4690k 4.5 gb
gtx 970 no Oc at the moment
10 gb memory
Running the cv1 on vr low with de-bug tool set to 1.5
Sorry if it's I've missed something as so frustrated at the moment many thanks
Rob
Starting to be impossible to play
I5 4690k 4.5 gb
gtx 970 no Oc at the moment
10 gb memory
Running the cv1 on vr low with de-bug tool set to 1.5
Sorry if it's I've missed something as so frustrated at the moment many thanks
Rob
Frontier don't support users with less than 16GB memory for VR. 16GB is the minimum.
I run with no page file and 16GB ram and have done for many years. Never had any issues. Nor do I experience this memory leak/crashing. Last night I was happily playing away for about 4 hours with my CV1 and not a problem in sight.
- - - - - Additional Content Posted / Auto Merge - - - - -
I've never managed to get this debug tool for the Oculus to stop washing out the colours and killing the framerate not matter what per pixel rendering is set to. Anyone else see this and do they have a solution?
Last edited:
I was having this problem too. 16 GB ram. Set your page file to Auto, or windows managed, whatever it's called in your windows version. Needs a reboot to take effect.
The game commits a very large amount of memory, I find especially when you load the galaxy map. It does not use that memory. The error you get is because you run out of commit memory. Because windows cannot expand your pagefile to make room for it. There's TONs of bad information on the net about pagefile, this thread is already starting to collect some of it. Don't believe me if you like, but setting pagefile to auto will make the memory errors go away.
The game commits a very large amount of memory, I find especially when you load the galaxy map. It does not use that memory. The error you get is because you run out of commit memory. Because windows cannot expand your pagefile to make room for it. There's TONs of bad information on the net about pagefile, this thread is already starting to collect some of it. Don't believe me if you like, but setting pagefile to auto will make the memory errors go away.
I've not had any memory issues at all. I have 16Gb and the default windows settings with regards to pagefile etc.
Yep, one problem with the Internet is old information hangs around and gets regurgitated as current when it's long been not relevant anymore.
Any Windows version from 7 onwards handles everything from pagefiles to defragging hard drives perfectly well on it's own. Don't mess with it.
Yep, one problem with the Internet is old information hangs around and gets regurgitated as current when it's long been not relevant anymore.
Any Windows version from 7 onwards handles everything from pagefiles to defragging hard drives perfectly well on it's own. Don't mess with it.
But the main thing is the people who raise an issue but don't realise they need 16GB minimum for VR. Maybe it actually needs the direct action of a loading screen or home page in VR mode that clearly states the computer requirements?
Well I took good advice and updated my ram to the recommended 16 gb and it fixed the problem
Looking at afterburner and it still steadily rises. I played for three hours yesterday when I finished it was on 9000 + mb and still rising very slowly. Was quite shocked it took that much but pleased I can finally play for more than 30 mins
Looking at afterburner and it still steadily rises. I played for three hours yesterday when I finished it was on 9000 + mb and still rising very slowly. Was quite shocked it took that much but pleased I can finally play for more than 30 mins
16GB doesn't fix the problem, it simply buys you more time. Anyway, as mentioned previously, the devs are aware of the issue
Interesting thread about memory leaks.....
I recently fitted an SSD to my system as main drive..
a tech friend said that as I had 16gb of RAM and an SSD there was no real need for a pagefile.
I was a bit sceptical but I tried it.. I could always go back and set a pagefile if I wanted to.
I am running w7-64 pro NO page file..
I have NO crashes.. no lockups.. no issues at all with any programmes or games.
ED Horizons runs fine..locked at 60fps using ingame settings..1.5x supersampling.. most other settings are medium to high..
Maybe 2-3 seconds pause coming out of Orbital Cruise/Glide..but planet textures load fast enough that it doesnt break my immersion.
Every PC is different.. some people are just lucky I guess.
I am not a techy-type person but I have built a few PCs the last 20years.
One thing I have got into the habit is NOT to run unnecessary progs at the same time as the main prog I am interested in.
I dont run windows auto-update.. or skype or Geforce experiance.
Sorry for the ramble but my pain meds just kicked in
Edit : 30mins of monitoring ED resources thru the task manager memory monitor..
EliteDangerous64.exe and EDLauncher started at 3046Mb usage and crawled up to 4974Mb
and apologies to OP I dont have VR I didnt see this was in VR forum section
I recently fitted an SSD to my system as main drive..
a tech friend said that as I had 16gb of RAM and an SSD there was no real need for a pagefile.
I was a bit sceptical but I tried it.. I could always go back and set a pagefile if I wanted to.
I am running w7-64 pro NO page file..
I have NO crashes.. no lockups.. no issues at all with any programmes or games.
ED Horizons runs fine..locked at 60fps using ingame settings..1.5x supersampling.. most other settings are medium to high..
Maybe 2-3 seconds pause coming out of Orbital Cruise/Glide..but planet textures load fast enough that it doesnt break my immersion.
Every PC is different.. some people are just lucky I guess.
I am not a techy-type person but I have built a few PCs the last 20years.
One thing I have got into the habit is NOT to run unnecessary progs at the same time as the main prog I am interested in.
I dont run windows auto-update.. or skype or Geforce experiance.
Sorry for the ramble but my pain meds just kicked in
Edit : 30mins of monitoring ED resources thru the task manager memory monitor..
EliteDangerous64.exe and EDLauncher started at 3046Mb usage and crawled up to 4974Mb
and apologies to OP I dont have VR I didnt see this was in VR forum section
Last edited:
I'm having the same problem right now. I didnt notice it as much before the most recent update, but I might not have been making as many jumps as I do now. Still new to the game, so take that into consideration.
Also, I was on 8gb of ram and it took hours for me to run into any memory issues. Now after the update it was running out of memory within a half hour. So I added more ram to a total of 16gb and I thought I was good. But after 2-3 hours I run into the problem again. Almost my complete 16gb in use and it locks up the rift view until I close all the windows and restart.
Starting to really get into this game but there is definitely a memory leak issue that needs taken care of.
Also, I was on 8gb of ram and it took hours for me to run into any memory issues. Now after the update it was running out of memory within a half hour. So I added more ram to a total of 16gb and I thought I was good. But after 2-3 hours I run into the problem again. Almost my complete 16gb in use and it locks up the rift view until I close all the windows and restart.
Starting to really get into this game but there is definitely a memory leak issue that needs taken care of.
Hadnt had it for a couple of weeks, but id only been playing fairly short sessions - played for a few hours last night and it happened twice
Bumped the bug report
https://forums.frontier.co.uk/showt...ing-Windows-OOM-message-and-Rift-image-freeze
Bumped the bug report
https://forums.frontier.co.uk/showt...ing-Windows-OOM-message-and-Rift-image-freeze
Is your pagefile at 16GB?
Yes. It was before and after I added the new ram. Its a lot more playable now, but the usage still continues to creep up without ever stopping. Even if I had 32gb it would eventually reach it if I continued to play long enough without closing it out. It would just take longer.
I used to run into this problem all the time and upgrading to 16GB (from 8) did not fix it, just made it longer until I got the egg timer.
The only way I have found to stop this from happening is to stop using the Oculus Debug Tool and ED Profiler and just rely on the (crappy) in-game SS settings. It sucks but at least it doesn't crash.
The only way I have found to stop this from happening is to stop using the Oculus Debug Tool and ED Profiler and just rely on the (crappy) in-game SS settings. It sucks but at least it doesn't crash.