Photo 1.9 hangs when batch converting CR2 files to JPG

[Alex_M]

Affinity Photo 1.9 hangs when I try to batch convert more than 3-4 CR2 files to JPG at a time. The circles just keep spinning forever. RAM usage also jumps through the roof - 16 gigs (I have 64 gigs so this should be fine). Photo processes them fine if I do only 2-3 CR2 images at a time. Unfortunately, I have to batch convert hundreds of CR2 files to JPG and this is going to take lots of time by the looks of it.

See screenshot below.

[Mark Ingram]

@Alex_M, what is your RAM limit slider set to in Preferences?

[Alex_M]

It is set to 32768 mb.

BTW, does Photo really need tens of gigabytes of RAM to process ~15 RAW images weighing 400mb in total? Is this normal?

[Gabe]

Hi @Alex_M,

Did you notice any difference in 1.9.1? 

[Ron P.]

FWIW, I have not had any hanging while batch converting CR2 files to jpg. I converted various numbers up to 15. I had task manager running during this, and noticed my Memory usage did climb to around 12,000+ MB, CPU of course at %100, GPU only around %4.

Knowing this would be very heavy task for my old machine, I done the following before running the batches.

• Disabled from the internet
• Disabled my anti-virus
• Disabled UAC

I tried both saving the converted files to the same drive as the CR2 files, and to an USB external drive. I also ran them with and without Parallel Processing enabled.

*My video card Nvidia GTX 645 does not qualify for the OpenCL so it was not enabled. *

Just a side note; I learned years ago, while I was a moderator and then Administrator for Corel (originally Ulead) help forums, to set up a profile to edit videos using their programs, Ulead MediaStudio Pro, and VideoStudio. I learned this from a college, where the profile would have the bare minimum services running. Might ask why do that? To get the job done, without having hanging and crashing,= fewer headaches. Some tasks ask a lot of a computer, sometimes I think, more than what we think they're capable of.

[nCubed]

Windows 10 x64
i7-6700 @ 4.00Ghz (4 cores / 8 processors)
16GB Ram (high speed gaming)
Affinity Photo v1.10.1

Same issue with crashing while batch converting several CR2 files to JPEG (or really any exported format). While monitoring the conversion process, I noticed the CPU spiked and maxed out, as well as RAM through the roof.

The underlying issue is Affinity Photo is defaulting to "parallel processing" (small checkbox in the lower left of the batch convert UI) and the code is not correctly managing the parallel process.

Once I disabled "parallel processing", the conversion process completed without error. And actually converted as fast, if not faster than parallel processing when testing with small batches, re: small batches of 5 or so images did not crash the system.

I haven't tested this theory (and not going to; Affinity needs to do their own testing), but I suspect a batch process with more images than processors available, or some multiple of cores/processors) is the culprit in the code base.

Cheers!