Search the Community

In V1 of Affinity, I was able to override the RAM Usage Limit (or at least I think it was overridden) to a value larger than the slider range by manually typing a value into the field. I believe this static range was subsequently fixed, although I'm not certain of that In V2, that no longer works. It resets to 65536 MB. Yet I have 128GB in my machine. So why is this slider range not being set to 0 - "Maximum Physical RAM"? I frequently have all three products open simultaneously with several files loaded in each one. It would be nice if Affinity products could actually exploit all of the RAM I have.

After upgrading to Affinity Photo 1.10.3. yesterday, I (temporarily) reenabled hardware acceleration on my machine, to verify whether some freeze problems that I encountered recently were solved with the latest release. The findings of my earlier tests with previous releases are documented in detail in a different thread (https://forum.affinity.serif.com/index.php?/topic/150705-affinity-photo-hangs-after-doing-some-hdr-merges-panorama-stitching-memory-leaks/). Unfortunately, the freezes are still there😡... While I'm testing problems with AP, I focus particularly on how AP manages memory, because my feeling (suspicion) is that something is broken there. During my latest tests after installing the 1.10.3 release, I noticed something strange. In my AP Preferences, the 'RAM Usage Limit' is set to 16383MB (see screenshot below): In total, I have 32 GB of physical RAM (and 12 GB of VRAM). When running some test cases, I verified the memory consumption via the 'Processes' tab of the Windows Task Manager. There, I saw that the memory consumed by Affinity Photo raised till levels above 27 GB (see screenshot below): How is this possible, when the parameter in the AP Preferences (Performance tab) restricts the RAM usage to 16 GB?? The reason why I find this bizarre (and why I report it separately) is that such situations with high RAM/VRAM usage are typically (i.e. very often!) a precursor for system freezes shortly afterwards. PS: When I disabled hardware acceleration later on again, it appears that I can't reach the same levels of excessive RAM usage. Then, AP rather obeys the constraint of the Preferences parameter, although sometimes with a small surpass. From my earlier tests (see also link above), I've learned that there appears to exist a mechanism that kicks in once the RAM limit is approached. That mechanism seems to release RAM. Indeed, With HW acceleration switched OFF, AP behaves (in general) relatively stable. With HW acceleration ON, such memory release mechanism doesn't seem to happen (or at least not always in a timely manner)...