Self-contained Yafc uses 4GB of RAM on Windows 7

[mrSumkin]

First I want to say thank you for such a quick response to my suggestion of a self-contained bundle.

I tested the new build on Windows 7 and got some interesting results.

1. It works. I haven't tested it for a long time but it looks like it works.
2. After startup, the computer loses 4+ GB of RAM. It is consumed as System and does not show up as yafc process memory. So it can be unclear what happens after the program starts.

I don't know why this happens, I compared a similar build of another program where .NET 6 was built in, and I didn't see anything like this there.

I don't know if this can be fixed, and if anyone will fix it, anyway, thank you very much for your work.

[mrSumkin]

I forgot to mention what I think is an important detail.
I rebooted the system, started yafc and it started quickly, but memory was wasted. It's not like loading 4 GB libraries from disk or something. It looks like it was cut off for some kind of reserve. Usually heavy applications take a while to load from HDD. I was specifically running yafc from HDD to see what is going on.

[DaleStan]

Can you show us the values/graphs you're looking at? Also, if you have .NET 6 installed, will you check to see if old builds of Yafc-CE have the same problem?

I suspect I know what you're seeing, and if I'm right, it's probably a Win7 thing:
The short version is that Yafc (both stand-alone net8 and an older framework-dependent net6) tells Windows "Please be aware that I might require thus-and-such ability in the future." Windows makes a note to itself, and a naive implementation of virtual memory requires just over 4GB to make that note. Newer processors and/or OSes (including my Win10 plus 12th-gen Intel computer) can store that note in 8MB or possibly just 16KB.

There may be a knob you can turn somewhere to adjust the request, but I wasn't quickly able to find it.

[mrSumkin]

Can you show us the values/graphs you're looking at?

Look at System and Kernel memory

Process explorer -> System Information

In windows we can look at Memory, but nothing interesting

Or process info in Process Explorer

Also, if you have .NET 6 installed, will you check to see if old builds of Yafc-CE have the same problem?

No I don't have NET 6 installed on that notebook but i have an other Application (ModShardLauncher) with NET 6 bandeled. Net 6 can't be installed on win 7.

ModShardLauncher works fine. Look at System and Kernel memory:

[DaleStan]

My theory doesn't work in that case. I'm seeing both a 2 TB and a 256 GB reservation, which adequately explains 4.5 GB of page table entries (system memory), assuming the OS allocates the PTEs eagerly.

It looks like you're only seeing the 256 GB reservation, which only explains the ½ GB of page table entries, not the other 4 GB.

I don't see the same value names in the System Information window that you do, but none of them are showing anything that looks like a 4 GB jump when I open or close Yafc. With it running, I see this:

[mrSumkin]

I don't see the same value names in the System Information window that you do, but none of them are showing anything that looks like a 4 GB jump when I open or close Yafc. With it running, I see this:

I could not find an exact description of the System parameter, so we can assume that System = Kernel. In current versions of Process Explorer there is no System.
I don't know where this memory goes yet, but I'll think about it. This 4 GB is not reflected anywhere in any process. And I don't know how and where to track them in detail yet.

[mrSumkin]

I get exactly the same thing on this laptop when starting Unity Hub. Needed to start Unity and I got the same problem with the Kernel memory. It's enough just to run the file responsible for checking the license. You don't even have to run Unity itself.

[Dorus]

Can you use RAMMap to figure out where the mem is going?