1Mac, on 15 February 2019 - 05:03 PM, said:
I finally was motivated to do a test with a fully modded install and a 64-bit prefix. The result was much better, more stable memory usage. I crashed out at 2.6 gb, which is actually consistent with what a LAA program is supposed to do ("4gb patch" is a bit misleading).
Which is to say: for large address aware programs, it does make a difference whether you are using a 32-bit or 64-bit prefix.
(What I'd like to know now is why fonts and menus that are perfectly fine with a 32-bit engine are all messed up with a 64-bit one. This pertains to both Wine functions like wineconfig and to tools such as mod managers and the like.)
Iâ€™m not sure why your getting a font issue as I have freetype set to 35 rendering mode for all wine/-preloaded/wine64/-preloaded processes in my current wrapper versions as needed.
(Newer wine versions support the newer freetype rendering modes anyway)
1Mac, on 15 February 2019 - 06:52 PM, said:
Mac OS Activity Monitor.
I'm not sure what you mean by 32bit vs 64bit LAA. I thought LAA patching was something you did to 32bit programs so they'd make better use of memory available in a 64bit environment. LAA patching a 64bit program seems redundant, but I'm probably missing something.
As it happens I was running a Wine 3.19 64bit engine. I wasn't explicitly testing this issue when I figured this out, so I wasn't being particularly rigorous. I can do a more formal test with the latest 32 and 64 bit Wine engines for the sake of certainty.
If you want to get better testing results overall might want to use Wine4.0/Wine-4.1 those had a lot of improvements over the earlier 3.x versions. I had good results for my usual games using these versions.