Stuck when batch processing in parallel .dng into .png on Threadripper pro

[Michael Tran]

Windows 10 Pro latest version, Lenovo P620 with 256 Gb ECC RAM, Threadripper Pro 3975X,  RTX A6000 latest drivers, files stored % written either on SSD or on HDD. Latest version of Photos. I experience a crash whatever option I check when job batching in parallel :

I have ~100 .dng files of 48Mpx from an honor view to convert to .png, 16bit and with no other adjustments. It starts by attempting to load all files at once, requiring as much as 160Gb of ram, lots of storages access and CPU and GPU as well (once I disabled the open CL computation it made no difference) and it got stuck after dumping about 35 .png files and did not carry-on with following files still displayed as "loading". At this point CPU load dropped to 2% (in average, since there are 64 logical cores), but both RAM and GPU memory keep being occupied with the same amount (like 160Gb RAM and ~40 Gb in VRAM) and with no variation at all over time and no storage activity indicating that the process somewhat crashed but there no error message no nothing.

It will take me much longer to batch convert these dng without parallelisation (I check it works so files are fine) so this feature is mandatory for my regular work. The batch processing on the same files works fine on another PC with just 8 physical and logical cores.

What's happening ??

Is the parallelisation a dead feature on Threadripper ? Could the option be given in a future release on how many parallel process should be undertaken ?

Thank for your input.

 

michael

 

[Chris B]

Hey MIchael, welcome to the Affinity Forums.

The developers are aware of the problem. For now, are you able to work around this by reducing the batch count? I appreciate this isn't ideal and your machine should be more than capable but until this is fixed, it is the only workaround I can think of