https://bugs.kde.org/show_bug.cgi?id=479870
Michael Strothotte <michelist.tracksb...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michelist.tracksbugs@yahoo.
| |com
--- Comment #5 from Michael Strothotte <michelist.tracksb...@yahoo.com> ---
At first, I wanted to write that I can confirm this error. Now I have to write
that I can partially (or halfway) 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.
I terminated Krita via the task manager.
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?
If you find this can be called confirmed, then I ask you to set it to
confirmed, in my eyes, this is very unclear / hard to grasp.
Michelist // Michael Strothotte
--
You are receiving this mail because:
You are watching all bug changes.
