Memory Leak

Toekiller

T
Hi, I have an issue that's driving me insane. Using Oculus CV 1, playing Elite Dangerous 2.1. After a while 15 - 30 mins, I will get a memory warning, usually elitedangerous.exe and the game will slowly die or crash.

Windows 10 64 bit, Inno 980 TI. 8 gig. Starting elite from launcher.

Anyone else? Any idea's?

Seemingly only Elite and I can make it crash very fast by upping the sampling rate.

Thanks.

Toe
 

Toekiller

T
Hmm could be though I don't lose any performance. The game will crash or the cv1 will lose a panel or go black.

Nothing of note in the background. Very few services running.
 

THE BLOB

T
I get the same problem with the dk2 egg timer crash and low memory elite.exe restart its fine again but usually happens after an hour or so. And only started happening recently

i5 4690k 4.5 ghz
gtx 970
10gb ram
 

Drexel Viehbock

Drexel Viehbock
I had the same exact problem. Sadly, the only way I fixed it was to up my main system RAM to 12 gigs from my original 8gig. I did have some success while still at 8 gigs using this method.

1. End all programs not essential to EDVR.
2. Launch Oculus software.
3. run task manager and end the explorer.exe process.
4. End task manager.
5. Put on HMD and launch Elite.

It worked for me until my new RAM arrived. I think it is the Oculus runtime which has the problem. Before my CV1 arrived, I still had 8gigs, and my VIVE did not have this problem with Elite.
 
Last edited:

jannix

J
Same problem for me. Windows 10 will pop up a window warning ED 64-bit exe is using too much memory and we are running low on system resources. If i don't quit and restart the game when that happens, a few minutes later the game would simple crash. I am guessing Windows is crashing the app, which is why there is no error log generated. It takes about 1 hr of game time for me to see this.

I really hope Frontier sees this problem locally to hook up a debugger and see what is happening.
 

subsy

S
I have the same issue - only happening since the 2.1.02 update.

16GB RAM / DK2

- - - - - Additional Content Posted / Auto Merge - - - - -

I forgot to add - usual behaviour is that the DK2 screen freezes - game still continues in second window on monitor, but needs to be quit / restarted to get the memory footprint back to normal
 

Toekiller

T
A possible solution. Not yet confirmed. Using msi afterburner, I noticed my pagefile 4 gig was being fully used. Upped it to 8 and it seemed to take longer to crash.
 

shadragon

shadragon
Beachlight7 said:
Have you tried setting it to 32gig, will it take even longer to crash or no crash?
Click to expand...
Pagefile is typically used when RAM is no longer available. Pagefile is also a thousand times slower than RAM. Making it larger only offsets the issue. I have Win 7 so this may not be 100% the same but hit CTRL - ALT - DEL then START TASK MANAGER. Click on PERFORMANCE tab then click RESOURCE MONITOR. On that window, select MEMORY tab.

Start E: D. When you are in your ship on the pad, ALT - TAB to the Memory window and make a note of how much RAM the E: D processes (Launcher and Client) are using. Play the game. When you experience issues, ALT - TAB back to Memory window and make a note of how much RAM is being used for both again. If no, or little change then it isn't E: D. If it is either Frontier program, note which one and report back. You can also open a ticket with that info as backup.

I don't experience any loss of RAM or slowdowns so not sure if it's Win10 related or not. More info you can gather the better. Cheers.
 
Last edited:

Toekiller

T
Hello! Ok update. Put 16gb into machine and upped the page file to 16gb. No crashes all night on 1.5 super sampling. I believe it's more to do with expanding the page file as i'd put 12 gig of memory earlier in with no difference. I've monitored the memory during a crash and it's always been at 50 /60%.

I've raises a bug report.
 

Stygian

Stygian
Has anyone tried setting pagefile to zero? It may be a bug specifically with page file usage. Also, as noted above, excessive pagefile will only slow down your system as it is only as fast as your HDD read/write. (Note that SSD users should really have already done this)
 

shadragon

shadragon
Stygian said:
Has anyone tried setting pagefile to zero? It may be a bug specifically with page file usage. Also, as noted above, excessive pagefile will only slow down your system as it is only as fast as your HDD read/write. (Note that SSD users should really have already done this)
Click to expand...
Don't do this whether you have SSD or not. MS accesses the PageFile for routine calls and setting it to zero will cause instability and eventually a crash.

As a rule of thumb, the PageFile should be set to the amount of RAM you have in your system. As an absolute minimum on Win7 or earlier no less than 512 MB, for Win8 and later 1GB to handle crash dumps properly. I fix the size of my PF to a static value so the PC isn't continuously resizing it and have it on a different HD than my OS. If you are not a techie, just leave these settings alone.

Here's a LifeHacker article from a few years ago, but it is still valid.
 
Last edited:

777Driver

777Driver
Have been talking to support directly - This is the latest reply

QA are looking into this issue but no workarounds currently, please keep an eye on those threads, but this may be something we need to patch sorry.

As you and the threads mention it does seem to be a memory leak.

Best regards,
 

subsy

S
777Driver said:
Have been talking to support directly - This is the latest reply

QA are looking into this issue but no workarounds currently, please keep an eye on those threads, but this may be something we need to patch sorry.

As you and the threads mention it does seem to be a memory leak.

Best regards,
Click to expand...

Thanks 777
 

Hempstead

Hempstead
Mine does slightly different.

Win 7 Ultimate, 16GB RAM. R9-290X (2x, and of course I had to turn off CrossFire for CV1).

Whatever gfx setting I use, VR-High, or VR-Low... on my trade route (3 jumps each way), at precisely 9th round trip, the FPS will drop from 90FPS to single digit, stutter like hell. If I leave the game on overnight and just sit in the dock, no problem. The only way I found to resolve the problem was to restart ED, as well as Oculus client.

Going to Maia from around Achenar... I could never complete the trip without having to restart ED/Oculus.

It's beginning to look like after certain # of jumps, some memory or some cache limit got reached and FPS start going to single digit. I mean, on my trade route, it's always the same 4 systems that I jump in and out, so it shouldn't need to cache more system data into cache, if there is a cache. But going to Maia, they are all different systems, and after certain # of jumps, the low FPS problem also happened. Very puzzling...

Also, I noticed. When the low FPS problem happened, if I quit ED, and as soon as I got back to Oculus Home, the Oculus Home would stutter for a few seconds, then it would smooth out. At this point, if I did not quit Oculus Home, and started ED, it wouldn't work (I had to let ED launch Oculus Home/Client, or it wouldn't display ED in CV1). So, I can't be sure whether it's ED or Oculus is causing this problem.
 

neveser

neveser
I having issues as well. About 2-3 hours in, I start getting the warnings from Windows.

Win10
i7-3770k @4.5GHz
16GB RAM
 
You must log in or register to reply here.
Back
Top Bottom