Bug 452609

Summary: corrupted layers when scaling and then moving
Product: [Applications] krita Reporter: myway880 <myway880>
Component: Tools/MoveAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: major CC: dimula73
Priority: NOR    
Version First Reported In: 5.0.2   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description myway880 2022-04-14 12:08:46 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  scale a layer 
2. while it is still processing start pressing  the key shortcut for move operator and move
3.  I'm working with a huge file (6G 36.693px * 21.949px ) there is a lot of lag  

OBSERVED RESULT
the layer get corrupted and become empty, visible in the layers stack and when you start a new move operation it will complain that the layer is empty. while the preview in the canvas still looks normal if the user saved at this point , he will get a corrupt file. undo doesn't restore the layer content and sometimes cause a crash or hang the GPU, my own guess "a race happening where the move start working before scale operation is fully done and it gets an empty layer and leave it like that when it finish"

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Dmitry Kazakov 2022-04-18 12:12:42 UTC
Hi, myway880!

I'm afraid I cannot reproduce the issue. Could you share some kind of screen recording of the issue? Perhaps I do something wrong?
Comment 2 Bug Janitor Service 2022-05-03 04:35:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-05-18 04:35:30 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!