easy to reproduce crash

[jjg61]

Open Affinity photo

drag small image

select sample color

delete key

document / unselect transparent background
control s

control w

repeat for an hour or 2

will crash affinity photo consistently and sometimes affinity will not restart unless you contorl-alt delete and kill the stuck affinity program.

 

sample photo attached

 

[Chris B]

Hey jjg61, welcome to the Affinity Forums.

On 6/18/2019 at 1:34 PM, jjg61 said:

repeat for an hour or 2

 

Do you mean you have sat and repeated this over and over for 2 hours or do you mean after 2 hours or so the crash will happen?

[jjg61]

I needed to remove the background from 2000 small images.

Affinity crashed a few times during this job that lasted about 5hrs.

So the interval between crashes was between 1 and 2 hours. 

I was doing this sequence very fast.  It was like an endurance dexterity test.

[Chris B]

On 6/21/2019 at 8:46 PM, jjg61 said:

I was doing this sequence very fast.  It was like an endurance dexterity test.

You didn't happen to open Task Manager and notice if the memory was running out? I can have my apps open all day without a single crash, however I'm not working to the extremes that you are so it could be the way we're managing the memory. 

[jjg61]

7 hours ago, Chris B said:

You didn't happen to open Task Manager and notice if the memory was running out? I can have my apps open all day without a single crash, however I'm not working to the extremes that you are so it could be the way we're managing the memory. 

Leaking memory is considered a bug in programming.  When the previous image is closed, its memory should be released.  My system has 64GB,  that could explain why it took so long to crash (ie: bug needed to leak memory from many images before running out).

Anyhow, the impact on me was not great. Restarting the app is pretty fast. 

Typically programmers like these intermittent but reproducible faults since they often rear their heads in non-reproducable ways that are near impossible to bebug.  Just image, you work for an hour or two doing all kinds of operations and the program crashes. What action of the many hundreds caused the issue.  Users are left with a bad feeling of a flaky program. In my scenario, the same action over and over causes the issue, so a designer can debug and fix. In doing so, they probably solve many other mystery crashes.