Schlichi Posted July 3, 2021 Posted July 3, 2021 Hi, I am on Windows. Removing tripods from panoramas, I use the live projection. However, in the latest version, Affinity is crashing after a few steps. Always. And it didn't with prior versions and I am stuffed with RAM. The files are not small, I admit, but that has never been a problem at all. I am editing JPG with 24000 by 12000 pixel. And I am doing so since years. I am at the latest version (1.9.2 1035). After chosing equi in live projection, I am copying a clean part of the floor, pasting, dragging to the right position and now or just one step further, Affinity Photo is not coming back. It uses around 17000 of 64000 RAM and is using zero processing power. Any idea, why that can be? Again, I am doing so since ages without an trouble. Thanks, Martin Quote
Staff stokerg Posted July 5, 2021 Staff Posted July 5, 2021 Hi @Schlichi, Just so we can rule out openCL as being the cause of the crash, can you try opening Affinity and click Edit>Preferences>Performance and at the bottom of this window is an option for OpenCL, if that's ticked, untick it and close Preferences and you'll be asked to restart Affinity. Once restarted, try using the app again and let me know the results. If you still have the crash, try installing the latest beta from here and see if you have the same issue. Quote
Schlichi Posted July 5, 2021 Author Posted July 5, 2021 Solved. Hi stokerg, thanks a lot. That did the trick. Apperently. I was watching the usage of cpu and RAM closely. With OpenCL switched on (Nvidia RTX 2080 TI), the consumption of memory grew easily to 45gb and more after a few steps. Now, after switching OpenCL off, it is growing to around 13gb up to 16gb. Only when inpainting a larger patch it went to 20gb. With OpenCL switched on, I needed to quit Affinity Photo after each session to begin a new one because the memory didn't recover well and grew on top of the consumption of the last picture. Now it still doesn't recover completely, which probably is ok, but it swings around 11gb to 14gb with the program running and no picture loaded. Loading a new picture doesn't add up to the usage of the last picture. Not quite sure if I did express myself well..... Anyway, thanks again. Stay save, Martin Quote
Staff stokerg Posted July 5, 2021 Staff Posted July 5, 2021 3 minutes ago, Schlichi said: thanks a lot. That did the trick. Apperently. Okay great to hear You might want to look into making sure your graphics card drivers are fully up to date and even do a clean install of them, then try enabling openCL again. Also it would be worth trying the beta i linked in my last post, as that has some fixes for openCL issues. Quote
Schlichi Posted July 5, 2021 Author Posted July 5, 2021 Hi, so, driver wasn't that old but now it is up to date. But still with openCL switched on, the production release crashes. AND The beta does as well. However, with openCL switched off, I can continue working for now. I don't know if that helps, but attached is one of the files, I can provoke the crash with. Open => Layer-LiveView-Equi => do "something" like inpainting, copy/paste something, combine layers, user the healing tool, use the clone tool => end live-view... good night. Quote
Schlichi Posted July 5, 2021 Author Posted July 5, 2021 State when it dies: CPU 0%, RAM: 16.582,0MB, GPU: 0% Quote
Daniel Aubert Posted July 6, 2021 Posted July 6, 2021 Finally! So simple! That also worked for me! Thank you, @stokerg!!!! I am using Windows 10. Quote
Recommended Posts
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.