Bug 496466 - Clone layers deadlock?
Summary: Clone layers deadlock?
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Layer Stack (show other bugs)
Version: 5.2.5
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-19 15:22 UTC by thequver
Modified: 2024-11-27 08:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
clone layers bug (96.18 KB, application/x-krita)
2024-11-19 15:22 UTC, thequver
Details

Note You need to log in before you can comment on or make changes to this bug.
Description thequver 2024-11-19 15:22:04 UTC
Created attachment 175951 [details]
clone layers bug

***
I have a tricky setup involving clone layers that makes the programm stuck in an endless processing, preventing me from saving the image (file attached). I've found 2 ways to trigger it, unsure if those are related but i think it belongs to the same report.
***

STEPS TO REPRODUCE 1
1. Open the file, select move tool
2. Move layer named "1" (marked with the red color) very fast so it does not have time to update in viewport. 
3. 90% programm will stuck in processing "Move" operation

STEPS TO REPRODUCE 2
1. Open the file, select move tool
2. Move layer named "1" (marked with the red color) slowly to not trigger the bug, complete the operation
3. Move layer again slowly, complete the operation
4. In the "Undo history" panel press undo and redo until you trigger the bug
5. programm will stuck in processing "Updating"

OBSERVED RESULT
Program is responsive but not allowing to do anything because it "processes" something endlessly

EXPECTED RESULT
Move and undo/redo must complete without any issues

SOFTWARE/OS VERSIONS
Windows: 11

ADDITIONAL INFORMATION
Krita version 5.2.5 (git 454726a)
Comment 1 Dmitry Kazakov 2024-11-19 20:35:21 UTC
Hi, thequver!

Could you please test this bug in Krita 5.2.6? I guess the 5.2.6 release was made just specifically to fix this bug...
Comment 2 thequver 2024-11-20 14:33:14 UTC
(In reply to Dmitry Kazakov from comment #1)
> Hi, thequver!
> 
> Could you please test this bug in Krita 5.2.6? I guess the 5.2.6 release was
> made just specifically to fix this bug...

both ways are reproducible on 5.2.6 (git ab3502b)
Comment 3 Dmitry Kazakov 2024-11-26 10:35:01 UTC
Hi, thequver!

It seems like I fixed the bug in the stable branch of Krita. Could you test the nightly builds of Krita Plus? 

https://cdn.kde.org/ci-builds/graphics/krita/krita-5.2/

I can reproduce your issue in 5.2.6, but cannot reproduce in Krita Plus. So I believe it is fixed :)
Comment 4 thequver 2024-11-26 12:34:56 UTC
I tested the nightly build and can't reproduce it anymore, seems to be fixed! Thanks for your work
Comment 5 Bug Janitor Service 2024-11-27 03:46:32 UTC
🐛🧹 Thanks for your comment!

Automatically switching the status to REPORTED so the team can perform further triage.

In the future you may also do this yourself when providing needed information.
Comment 6 Dmitry Kazakov 2024-11-27 08:54:40 UTC
Thank you for testing! :)