Krita 3.3.1 update made me unable to work fluently due to constant freezes of the program, most notably while using the transformation tool, most of the time (at least not so much in a brand new canvas) when i use the transformation tool to tweak something and change to another tool in a rush the program will stop responding completly, but krita will not shut down, it will remain in that state until i close it forcefully or else wait a long time for it to give me a runtime error. Unfortunately it seems this is not a usual crash since it's not registered in the kritacrash.log nothing has appeared in the various crashes that have happened to me so far. It would appear this is what the documentation called a lock up of krita, therefore i can't provide a backtrace.
Hm, that's strange -- there weren't any relevant changes to the transform tool between 3.3.0 and 3.3.1. I haven't been able to reproduce either :-(
(In reply to Boudewijn Rempt from comment #1) > Hm, that's strange -- there weren't any relevant changes to the transform > tool between 3.3.0 and 3.3.1. I haven't been able to reproduce either :-( Hello, I've decided to try to be more helpfull and provide a video of my issue, i've uploaded it to my youtube channel. Link: https://youtu.be/kG_fzef2-IE In the video you can see that when i use hotkeys ctrl + t to change to the transformation tool, then to finish my transformation i just press the key b to start the processing as well as changing to the brush tool simultaneously, then right after pressing the key i start scribbling, then everything freezes and i have to close it down forcefully. This isn't always consistent, sometimes it won't freeze and everything will work out fine, however most of the time it does, the programm has also frozen in other instances where i'm not using the transform tool, but i havne't been able to determine what causes them, only the transform tool gives me that problem very often. I have also notice it's more problematic with larger files which contain a lot of layers and stuff.
I'm marking this as a duplicate of 383112. I stil cannot reproduce it myself, but we're getting this report quite a bit, it seems. *** This bug has been marked as a duplicate of bug 383112 ***