deanis
256 discussion posts
That's it? On Win7, my working set for DisplayFusion.exe is 60.1MB and DisplayFusionAppHook.exe is 9.6MB.
Yep, those numbers are all normal. Most of the memory that's allocated is overhead that the .NET Framework allocates when DisplayFusion starts up.
Thanks!
Saxamo1
4 discussion posts
Any Chance of getting DF to utilize .NET 4.5 which is installed by default in windows 8? vs having to install .NET 3.5 in addition? Or am I incorrect about the version it utilizes?