[INVESTIGATING]Diagnosis: Model/Livery browsing eating large amounts of memory?

[Worrazen]

Lately in recent month I was getting more "Resource Exhaustion" warnings than usual, including some crashes, then I saw that Commit of DCS.exe felt somewhat high than I saw in the past.

 

 

 

-------------

https://www.ibm.com/support/knowledgecenter/SSYKE2_7.1.0/com.ibm.java.win.71.doc/diag/problem_determination/win_memory_overview.html

 

Windows memory is virtualized. Applications do not have direct access to memory addresses, so allowing Windows to move physical memory and to swap memory in and out of a swapper file (called pagefile.sys).

 

Allocating memory is usually a two-stage process. Just allocating memory results in an application getting a handle. No physical memory is reserved. There are more handles than physical memory. To use memory, it must be 'committed'. At this stage, a handle references physical memory. This might not be all the memory you requested.

https://support.microsoft.com/en-us/help/2160852/ram-virtual-memory-pagefile-and-memory-management-in-windows

 

 

Keep in mind, MS it self does not keep terminologies/measures consistent across Windows utilities, so it ends up being confusing, some things also change with new version.

 

 

-------------

 

I had to stop basically posting large majority of the thoughts, which is just more about the windows memory stuff for those who are interested to know things in detail but it's not anything new or revealing besides the video, however I might do another video with more findings later on; because I figured out more bits about the whole Standby/Cached terminology which changed things quite a bit, so this thread will have more updates later on, the video is quite long and should be good in the meantime so I didn't want to hold the announcement back.

 

-------------

Video:

 

 

 

 

 

The very last frame before crash and end of the video:

 

 

 

The Windows DWM.exe and other Display and graphics stuff crashed to the point that a weird bizzare looking screen appeared with some kind of heavily blurred and corrupted resolution.

 

 

 

After replugging the DisplayPort cable; it didn't crash that hard.

 

 

 

DCS.exe frozen as expected, without crash report dialog. Forced termination worked okay, everything else seemed ok, but didn't tried running anything 3D again in that session.

 

 

I think this is well enough of a practical proof that COMMIT CHARGE is the primary memory measure everyone should be looking at, including all the in-game overlays built into games and I'm afraid the same goes for all of the 3rd-party game performance optimizer or graphics managers applications show in their stats, they probably show the same standard "In Use" or "Active" memory that's showin in the Task Manager Memory Graph, WRONG!

 

Which could mean that all this time, if you were watching various overlays for memory, or the Task Manager's graph, or the green bar in Resource Monitor, you have probably been seeing a number that's around 60-70% of total RAM being used.

 

And I was having such posts and discussions around here before about how misleading these stock Windows utilities can be.

Edited March 5, 2019 by Worrazen

[Worrazen]

Short version of the original video for fast preview:

 

 

[speed-of-heat]

bump great investigative work!

[Worrazen]

*** THREAD MILESTONE NOTIFICATION *** SIGNIFICANT TIME PASSED SINCE MY LAST POST

----------------------------------------------------------------------------------------------------------

 

Yah, this one I believe had a note in an update for "memory leak" fix shortly after but IDK if it's really or it was for something else ... I actually never got to around to checking it if it worked yet.

 

Actually this thread is prior, later I found out it's the encyclopedia that can cause it alon, missions just usually don't load up so much stuff in their lifetime except in big MP missions.

 

I kinda started digging into DCS diagnostics/performance testing at this point, then I got more organized so the videos will be more clearer in terms of OBS windowing/layering in the subsequent thread, check it out if you're interested:

 

https://forums.eagle.ru/showthread.php?t=236156

Edited June 25, 2020 by Worrazen

[JTFF - Raph]

Hi, I'm having the exact same issue, and I'm not finding solutions... I'm having CTD on every MP missions and also on SP if I set some units. My crashes are exactly the same, DCS crash, black screen, sometimes the video driver crashes. I can accelarate the passive memory leak while loading some liveries in spectator view. My 32Go are destroyed in a couple of seconds when I do this. Did someone find a way to fix this?

Edited July 15, 2020 by FrM | Raph

[BIGNEWY]

Sorry for over looking this thread, I have moved it to the crash section now, and have asked the team to take a look.

 

thanks

Edited July 21, 2020 by BIGNEWY

[speed-of-heat]

Thanks BN

[JTFF - Raph]

Up