jackmcbrezel Posted December 28, 2019 Posted December 28, 2019 Photo crashes when I hide an adjustment layer and afterwards show it again. I can reproduce the issue by performing the following steps: Navigate to the curves adjustment layer in the group Double click onto the layer and reset the curves Close the dialog Hide the curves adjustement layer in the layers dock Tick the visibility checkbox in the layers dock again in order to show the adjustment layer [crash] DSC07775-Bearbeitet.afphoto Quote
Imaginary Posted December 28, 2019 Posted December 28, 2019 Just tested your file here and Photo already crashes when hiding the curves adjustment layer at #4. Edit: Crashes even without modifying the adjustment layer. 1.7.3.481, W10 Quote
Ron P. Posted December 29, 2019 Posted December 29, 2019 @jackmcbrezel, Using your file it does cause a crash. However trying to replicate it, building the file from scratch, I can not make the program crash. I even used an image file, added a rectangle, deleted the image. From there finished building it, and following your instructions I could not make AP crash. Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
jackmcbrezel Posted December 29, 2019 Author Posted December 29, 2019 @Imaginary & @Ron P. thanks for checking my file. I fear I cannot precisely reproduce all steps that I did as I was playing around with some editing techniques. What I can say is that I got the original image into Photo from Adobe lightroom 5 via the "Open in external editor" function as a psd file. Then I duplicated the background layer and added some more layers (e.g. a red rectangle which I put into a group) and adjustment layers. I'll see if I can get reproduce the problem. And perhaps for someone who can debug the application it's not a big deal to find the issue (for me it looks like some null-reference or similar bug in the code). Quote
Staff Gabe Posted January 6, 2020 Staff Posted January 6, 2020 Hi all, I logged this with our developers. 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.