Affinity Designer 2 Memory Leak ?

[Klesk]

Im experiencing a different kind of behaviour with Designer V2. It starts up with like ~800MB Ram usage, but jumps up to ~2200MB just after a couple of minutes working in the same file (just moving around in an Artboard file). Yesterday it even start to lag with a Ram usage of 4400MB and shortly after crashed with strange UI artifacts. The Ram usage doesnt drop, it is slowly becoming more and more even when I delete stuff.

In total I have 32GB Ram and can ran multiple 3d editor tools at the same time. Did not test Publisher or Photo if they have the same issue. Any suggestions/updates/news ? 

[v_kyr]

Under which platform, Windows? - If yes disable under ADe inside it's preferences under performance settings the "hardware acceleration" and retry, in order to see if it now runs more smoothly without producing UI artefacts.

[Klesk]

Tested it out, same behaviour. Ok the UI artifacts thing ist just a byproduct of the actual problem. It seems that it is really a issue with the garbage collector (speaking now in dev-language). To reproduce:

create a artboard file, 
create a couple of artboards with a decent amount of textures, 
look at the increasing Ram usage. 
Now remove some of those artboards and look again at the Ram usage. 

For me nothing happens, still at the same high amount.

If you would save now and exit and open the file again (restarting AD), the Ram usage would be lower than before. So for me this means that garbage in the memory isnt thrown away :). Btw same counts for opening additional files in the same session (closing would not clean up my memory).

[v_kyr]

Don't know if they use(d) some add-on C++ garbage collector, but usually C++ itself doesn't come along with one. So as there probably isn't any auto garbage collector used one has to do memory handling explicitely yourself, aka allocate & free/delete memory on demand manually. Another point here might be, that due to their incremental file format and backup/history file handling any occupied memory isn't immediately freed up. - Though it's also possible that there are some dangling pointers still flowing around (not always deleted the right way) and thus occupied memory isn't released, which then would be more sort of memory leaks here.

Since I still use V1 apps under MacOS can't take a look at that in order to see if I can possibly reproduce that behavior, so someone else has to dive in here. - Further without source code in order take a closer look at it in a debugger and profiler it's hard to tell anyway.

[Klesk]

Totally agree, memory leaks are a pain ******* to find. Good thing is that I know there are some issues and I can work around by splitting up content. Ive read that some guys have also problems with photo 2 to edit multiple open files. Smells like the same issue. Strange thing is, that sometimes garbage is collected but sometimes its not. Will wait for future updates. 

Edited March 13, 2023 by Klesk
spelling