Photo 2 crashing trying to generate export JPG XL

[Legume8550]

Hi there!

 

I've being trying to export some photos taken with a Fujifilm X100V in jpg xl using my ipad pro 10,5 and the app always crashes.

Doing basic or just trying to export the image without any adjustments the export generation goes to 99% and crashes.

I'm attaching a totally black photo taken from the camera on used for the screen recording, but it happens with any .RAF file taken with this camera.

It doesn't happen when I export using a windows 10 machine.

 

Ipad Pro A1701 - Ios 17.7

Affinity Photo 2 - v 2.5.5.2636

(Because I was screen recording the app did take longer to open the file, it doesn't take that long when not screen recording).

 

DSCF5351.RAF

[walt.farrell]

Welcome to the Affinity forums.

Can you confirm which option under Open you chose? It doesn't look like you have Show Touches enabled in the application Settings, so I'm a bit unsure exactly how you started.

I can say that I've Opened your .RAF file and it exports to JPEG XL without crashing on my iPad (specs in my signature below), so I'm not sure why it might be failing for you.

[Legume8550]

I used import, but opening from photos gives the same result on mine.

I think is something about this memory or something on this iPad in specific, or the old ones at least.

[NathanC]

Welcome to the forums @Legume8550,

I can replicate this with your file but also using entirely separate documents on iPad, around the ~6000px width mark the app starts to crash specifically with JPEGXL. This is an issue i've previously logged previously on Desktop, but i've now updated the existing report to reflect that it's a more prominent issue on iPad.

[Legume8550]

1 minute ago, NathanC said:

Welcome to the forums @Legume8550,

I can replicate this with your file but also using entirely separate documents on iPad, around the ~6000px width mark the app starts to crash specifically with JPEGXL. This is an issue i've previously logged previously on Desktop, but i've now updated the existing report to reflect that it's a more prominent issue on iPad.

Thanks Nathan 🙂👍

I hope it gets fixed.