KlingonTarg

It's possible that the OS had shunted unused pages to disk and was just reloading them on exit to free up space. In which case, the bug would be more along the lines of 600MB per day (i.e. an even bigger leak). I'm just reporting what I saw in the hopes that the devs take a look at it.

All leak detection tools detect memory leaks based on memory no longer being attached to something. Some tools let you measure between two segments of code if you instrument the code manually. If an object uses reference counting and it gets into a circular reference situation, it can become nearly impossible to free the object until the application closes AND memory leak detection tools generally won't detect it because it DOES get freed when the application exits. I'm saying there is a 300MB per day memory leak in Affinity Photo that needs to be tracked down. That's a pretty significant leak.

Leaving Affinity Photo 1.8.3.641 on Windows 10 Pro (64-bit) running overnight (and not doing anything for many days) results in a roughly 300MB per day memory leak. After 10 days of just running in the background, Affinity used almost 3GB RAM according to Task Manager. I only had about a half-dozen SVGs open. When I closed Affinity down, it appeared to *allocate* an additional 3GB RAM while it was shutting down - reaching around 6.5GB RAM usage at peak. I have 32GB RAM, so it was able to cleanly shut down without hitting swap, but that's still kind of ridiculous. Probably some internal references not being released, so those resources are never freed until application shutdown. Most memory leak detection tools won't pick those kind of leaks up.

Underlying NVidia driver version is 419.35 (most likely not the latest).

In an effort to ween myself off of Photoshop knowing that my CS3 Extended license will likely stop working at some point in the next decade since CS3's been kind of buggy since Windows Vista, I've decided to give Affinity Photo a shot (I vehemently refuse to pay for Creative Cloud because I run Photoshop very infrequently and newer versions of Photoshop are really a non-starter in my preferred workflow). When I do the rare bit of image work, I mostly do vector art and screenshot image cropping. I was recently impressed with Affinity Photo's SVG support. I was able to import a few SVGs as vectors, readily make adjustments, and export as PNG. Took a little bit to get used to the tools, but the vector toolset is on par with Photoshop and superior to Inkscape (and, IMO, Illustrator). Will definitely use again for future vector-oriented projects (e.g. icon design). So today I attempted to use Affinity Photo for the first time to crop an image. In short: Nope. When cropping, I need pixel-perfect image crops of window screenshots from the clipboard (e.g. application screenshots for documentation) and Affinity is not particularly ready for that standard workflow out-of-the-box - especially the cropping part of image cropping. It took me but a moment to realize that the New Document dialog, which the startup splash screen encourages the user to use on startup, does not pay attention to anything on the clipboard. I had to cancel that dialog and locate the File -> New Document From Clipboard option to get the dialog to show the correct dimensions. It pasted the image for me too, which was fine. I zoomed in to 300%, which is the sweet spot for me for cropping in Photoshop and Paint.NET. I then activated the crop tool and attempted to draw a simple crop rectangle from the upper left corner to the lower right corner and...there's no scroll/pan support? I went back to Photoshop and had the crop done in under a minute. Panning the image in Affinity Photo for Windows also has very large flicker effects from double repaint/redraw operations plus some lag on a 6th Gen Intel Core i7 with a decent NVidia GPU. Good morning Windows GDI.