Komatös Posted March 30, 2021 Posted March 30, 2021 I have had the phenomenon several times now that when I undo steps with control + z, APhoto exits. Unfortunately, it cannot be reproduced specifically. Maybe you can find something in the dumpfile. In the log file is only the deactivated graphics card stuff. 4e330ec3-32ba-4a50-9d55-c455a96e09e3.dmp Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4061) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
Staff Chris B Posted March 30, 2021 Staff Posted March 30, 2021 Hey Komatös, Are you resizing anything such as the canvas? It's referencing the libpersona.dll which I've seen related to resizing before. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Komatös Posted March 30, 2021 Author Posted March 30, 2021 No, I had one file open and another placed as an overlay. Then I added a masking layer to the overlay layer. Then I changed the color model from 8-bit to 32-bit to reproduce the error with the blur and outline (the fraying). For this purpose I created a vector object and applied the effects to it. Then I pressed control + z several times until I reached the step of converting from 8-bit to 32-bit, I think. I can't say exactly, because APhoto left so quickly. Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4061) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
Staff Chris B Posted March 31, 2021 Staff Posted March 31, 2021 Perhaps it's the conversion then. I've just tried now and it seems OK but as you said, it's not an easy one to reproduce. I'll ask someone to peek at the crash report and see if they can spot something I might have missed! We may have a log of this already. I've just done some extensive searches of the database and found something that pretty much describes this. I've tagged your post to the report. Komatös 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
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.