https://bugs.kde.org/show_bug.cgi?id=382225

--- Comment #4 from Christoph <chrisvazquezvelazq...@gmail.com> ---
Created attachment 106558
  --> https://bugs.kde.org/attachment.cgi?id=106558&action=edit
Cache limit demostration

The actual file is quite big, but I found a way to solve the problem temporary.

I just lock the start and end frame, to a short amount of frame in the
timeline. For example, usually the program by default start at 0 to 100 frames
for fast preview when you play the animation, in the animation dock. If you
press play, the program will start a regeneration cache for those 100 frames
for consistence FPS value, otherwise the animation preview will be choppy. So I
lower the amount of frames preview per area, where I work, so that when the
program do background caching, it doesn't cache every frame from all layers,
just a chunk. This help me greatly, no more crashes. 

I did try Memory usage in Krita settings to see if I could stop Krita for using
more memory than what it was set to only use. Didn't work, but is
understandable, since I m using pictures of around 20mb .png files for the
rotoscope, and the cache process was fitting over 100+ frames in memory RAM.

It would be great if Krita have a way to disable background caching/
regeneration cache(only have it when you press play), just for this kind of
situation, or have a tool tips near the Start and End frame textbox, telling
the user a way to control memory usage, by limiting the amount of frames the
program pre-loads on memory before previewing the animation.

It save some headaches. I mean, the program stopped crashing, and I was able to
work the project all night no problem, just the usual re-start, here and there,
because the program don't flush cache, when I change the START and END frame,
it keep the cache on memory at all times.

Just look at your timeline, when you press play or try to move to another frame
with arrows, you see the bar below the columns, getting highlighted in grey.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to