Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Crash when creating largish panorama


Recommended Posts

I am using Affinity Photo 1.8.5.703 on Windows 10 on a quite powerful machine (Ryzen 2700X, 32GB RAM, NVidia 2070 Ti) and try to stich a largeish panorama of 30 shots. Unfortunately, Affinity Photo repeatedly crashes when creating the panorama. The program crashes

  • directly after creating the panorama, i just see a short flash of the window showing the stitched image
  • when trying to use any tool in the panorama editor, it's enough to click the tool icon to make afifnity photo crash
  • when minimizing and restoring affinity photo after the panorama has been stitched and is shown in the panorama editor

I don't think it's a memory issue since the total system ram usage is just 20GB according to Windows' task manager (so ~12GB left). I use Nvidia's studio drivers, so those should be quite stable. I uploaded the source files to google drive since they are quite large (1 GB): https://drive.google.com/file/d/1EZI_VKYCYUlnFZkEj-P_FObZWtHYS76r/view?usp=sharing

Some crash reports are attached to the post.

reports.zip

Link to comment
Share on other sites

How much memeory is allocated to Photo? I have 12Gb out of 16 installed

During the panorama creation the memory usage was about 3.5Gb with 34% cpu

During the next render phase it changed as the screenshot below, so 12 isn't enough as it's using the disc

Then clicking apply took yonks and smoke appeared out of the vents!

Astonishing detail of the birds!

MemorySetting.png

TaskManager.png

Microsoft Windows 10 Home, Intel i7-9750H CPU @ 2.60GHz, 16 GB RAM, 500GB SSD, 1TB Whirlygig, NVIDIA GeForce RTX 2060
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

Hi David, thanks for taking a look at my problem!

I checked the performance settings and it looks like RAM limit was already at 32GB:

affinity.png.a2b27e55c6611f599e835364cb3f7125.png

 

I thought, maybe that is too much, since 32GB will never be fully available, so i lowered it to 20GB and tried again and nothing changed. I tried to create another panorama and watch memory usage. I can confirm that it peaks at ~12GB. This time rendering the panorama completed, but just clicking on the "Transform Source Image" icon crashed Affinity Photo.

Link to comment
Share on other sites

Well your PC setup beats mine but mine works so there must be a solution. Maybe increase the File Recovery Interval, maybe - just maybe, this starts before the panorama has finished and causes chaos. I think you'll get better advice in the Affinity on Desktop Questions (Mac and Windows) forum so I'll report this post and hopefully the Mods can move it

Best of luck

MemorySetting2.png

Microsoft Windows 10 Home, Intel i7-9750H CPU @ 2.60GHz, 16 GB RAM, 500GB SSD, 1TB Whirlygig, NVIDIA GeForce RTX 2060
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

I tried increasing the file record interval but with no success.

Then, just for fun I tried changing the renderer to WARP. And this actually fixed the crashes. Right now, this is 100% reproducable for me, WARP -> no crashes, NVIDIA -> crashes.

I noticed that I still had MSI Afterburner running (allows to overlock the GPU). So I disabled it and tried again using NVIDIA, still crashes.

I am running NVIDIA drivers 460.89. Now, this could mean a bug in Affinity's render code or a driver bug. Is there anything I can do to help debug this issue, so that it is fixed in future versions?

Link to comment
Share on other sites

I increased the memory limit to 14Gb and tried again. Only Photo and two File Explorer windows open
After the Panorama finished and Photo was closed, the machine seemed very sluggish so I rebooted it before the WARP run. Strange that it took about 30s to turn off whereas it is usually instant

  Nvidia WARP
Add 78 18
Stitch Panorama 88 90
Render Panorama 144 162
Apply 15 54
  325s 324s

I don't understand GPUs and am lucky that mine works (studio drivers) but there's not a great deal of difference overall. Rather surprising that the Add stage is so slow with the GPU

Glad you have a solution and hopefully the Serif staff will see this and look at your crash reports

 

Microsoft Windows 10 Home, Intel i7-9750H CPU @ 2.60GHz, 16 GB RAM, 500GB SSD, 1TB Whirlygig, NVIDIA GeForce RTX 2060
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

1 hour ago, David in Яuislip said:

After the Panorama finished and Photo was closed, the machine seemed very sluggish

If Photo was fully closed, it shouldn't be able to affect machine performance. But even though the UI is gone, the application may still be running. You might try redoing this with Task Manager active, and watch the CPU and storage usage, as well as confirming when Photo is really fully closed.

-- Walt

Desktop:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.0 / Affinity Designer 1.10.6 (.1665)  and 2.0.0 / Affinity Publisher 1.10.6 (.1665)  and 2.0.0
iPad Pro M1, 12.9", iPadOS 16.1.1, Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.6 and 2.0.2 / Affinity Designer 1.10.6 and 2.0.2 / Affinity Publisher 2.0.2

Link to comment
Share on other sites

1 hour ago, walt.farrell said:

If Photo was fully closed, it shouldn't be able to affect machine performance. But even though the UI is gone, the application may still be running. You might try redoing this with Task Manager active, and watch the CPU and storage usage, as well as confirming when Photo is really fully closed.

Yes, you would think so. I watched progress in Task Manager and saw Photo release memory then finally quit, there was no evidence that I could see of any Photo remnants. I did the panorama again just now and it behaved the same. The odd thing is that I closed Photo and the two File Explorer windows then timed windows shutdown at 47s whereas it usually takes 2-3 

At the end of the day, thomas001le has a solution and I use Hugin so all's well

Microsoft Windows 10 Home, Intel i7-9750H CPU @ 2.60GHz, 16 GB RAM, 500GB SSD, 1TB Whirlygig, NVIDIA GeForce RTX 2060
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.