I tried from my side and yes, the bug is reproducible with @Grum999’s provided info and test file. However, my computer isn’t able to use the solution of converting to a zip file to get rid of the storyboard directory. Maybe because I use Windows, not Linux.
If I file a bug report on kde.org, I won’t have to change anything apart from the fact I use Windows, right?
In fact, .kra are just zip files; in file explorer you just have to rename file test.kra to test.zip for example, and then you’ll be able to access to content of file.
No need to crate a bug report for the case you’ve encountered here, I already opened it and provided everything needed for developer.
My question about someone else to test was to ensure that in configuration other than mine and yours, the problem as described can be reproduced 
Grum999
Anybody else is able to reproduce the case?
On dev side, it seems the problem doesn’t occurs…
Having more than me and @macaron to confirm if it’s occurs or not could help
Grum999
At first, I wanted to write that I can confirm this error. Now I have to write that I can partially confirm it. Tested on Windows 10 with two different installations of Krita 5.2.2.
For all the following tests, I created a blank file in DIN A6 portrait format, 300DPI.
Since yesterday I ran several tests, the first with my standard installation that has been running for days, which is “stuffed” with tons of plugins, bundles, brushes, gradients, i.e. resources en masse, the “resourcecache.sqlite” is almost 14 GB in size.
I used it to open “test_freeze.kra”, then created a new document, and was able to switch back and forth between the two documents at will. After about ten times back and forth, I scribbled something on the new document, and I started the animation and let it run, and then I could continue to switch back and forth at will.
Then I went back to bugs.kde.org to check the task to see if I was doing everything right, and when I switched back to Krita, Krita froze without generating any processor load. Okay, even if I didn’t expect it then, I should have expected it.
Next test with a fresh minimally customized version 5.2.2 on a different user account, with few plugins and hardly any extra resources, apart from ~700 MB ASL files (layerstyles) that I had forgotten, and a “resourcecache.sqlite” of about 380 MB.
With the installation I can still work without freeze after umpteen switches between documents, then playing the “animation”, then doodling on the new document, switching to any currently open application. I have now closed the files and ended this installation.
Next test yesterday evening, again with the “maximum installation” used in the first test.
After I started my standard installation again, I first loaded the file “test_freeze.kra” according to the bug report and then created a new empty project. After countless switches between documents, playing the animation, doodling on the new document, then switching between different applications, I can still use Krita without freezing. Since I had something else to do, I canceled after several switches.
Shortly afterward, I fell asleep and had forgotten/forgotten about the tests until I read your post.
That’s why I tested it just again, and again I was able to switch back and forth infinitely, paint on the empty document after a few changes, start the animation, but after switching to the browser and back, Krita got stuck again, but only shortly for ~20 seconds, since then it is running. Huh?
I’ll add this to bugs.kde.org
Michelist
Confirmed with 5.2.2 and the Jan 17th 5.3.0 pre-alpha appimages on Linux Mint 21.3.
Ok thanks!
Dumb question, how many CPU you have on your computer?
On my side I can see 24 thread starting when it freeze (then I have 24CPU)
I’ll try later to do test in a Linux VM, Windows VM, and my laptop…
Grum999
If it hangs again for me, I’ll report how many threads start, because I have to admit that I didn’t look at the detailed diagram in the Process Explorer.
Michelist
I have 8 cores and 8 threads, it’s a very old dual CPU arrangement
I didn’t look at the system monitor for individual CPU usage.
I have a total of 24 logical cores from 2 XEON’s built in 2014, so quite old too.
Should it possibly be due to the CPU manufacturer, or a new CPU function, a function that does not yet exist in the CPUs of @AhabGreybeard and me? @macaron, from which manufacturer is your CPU, and how old is it?
Michelist
I have used a Dell laptop, since July 2022.
I have dual Xeon E5450, first released in 2009. The PC is nearly 14 years old.
reading all this with interest…amazing work guys. Anyone tried the rename to .zip then unzip on a Mac successfully? I’ve given it a go and get an ‘unable to expand, it is in an unsupported format’
works using winzip for Mac. partial frame recovery using that method. Nice!
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.