Photo v2.2.0b1903 — crash when move mask from one to another layer

[znids]

1. Create New doc

2. Draw something on new layer, select it and create Mask

3. Make another layer and draw something

4. Drag mask from 1st layer to 2nd

5. Crash

Note: If first release mask from menu or drag it to release, and than drag to 2nd layer — it work fine

macOS 13.4.1 / ARM-64 / Affinity Photo 2 Beta 2.2.0 (1903)

[znids]

Now I see, same bug in AP 2.1.1 (1847). In AP 1.10.6 this work fine

[Hangman]

Hi @znids,

I've not been able to replicate this so far, are you able to create a quick screen recording showing the steps along with the crash?

[Chris B]

Hey znids,

I think you might be seeing a currently unresolved issue. The crash occurs as you drag the mask from its parent and hover under the next layer. You don't even need to release it... just hovering should get the crash.

1. Paint something with the Paint Brush Tool
2. Add a mask to it
3. New Pixel Layer
4. Paint something on it
5. Drag and hover the mask underneath the top layer > Crash

[znids]

22 minutes ago, Chris B said:

You don't even need to release it... just hovering should get the crash.

Exactly.

[znids]

41 minutes ago, Hangman said:

I've not been able to replicate this so far, are you able to create a quick screen recording showing the steps along with the crash?

May be you make blank mask for 1st layer, I tried that now, and drag mask to another layer works fine. But If you select your drawing by cmd-click on layer thumbnail and create mask, try to drag and hover it on another layer. I got crashed app

[Affinity Info Bot]

The issue "Drag-dropping a masked child layer out to the parent stack without releasing the mouse button causes a crash" (REF: AF-977) has been fixed by the developers in internal build "2.4.0.2252".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.