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.