https://bugs.kde.org/show_bug.cgi?id=382418
grum...@grum.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Version|3.1.2 |nightly build (please
| |specify the git hash!)
Status|RESOLVED |REOPENED
Resolution|NOT A BUG |---
CC| |grum...@grum.fr
--- Comment #1 from grum...@grum.fr ---
I reopen this bug, I'm not sure why it has been set to "RESOLVED/NOT A BUG"
Currently on Krita 5 (krita-5.0.0-prealpha-dba5ce5-x86_64.appimage), if
autosave run while an animation is rendering, render is stopped with a popup
message "failed to render animation frames”.
STEPS TO REPRODUCE
1) Create an animation for which time to render is long enough to have autosave
triggered
2) Ensure that document is in modified state (ie: the autosave will be
triggered)
3) Render animation
OBSERVED RESULTS
Render is interrupted, there’s a status bar notification "autosaving postponed:
document is busy" but rendering continues.
A couple of seconds after, there's a new notification.
This is repeated 4 times and then finally, autosave is applied.
A dialog box "waiting for image operation to complete (<updating>)" is
displayed for a couple of seconds and it stops the rendering with a "failed to
render animation frames" message.
EXPECTED RESULTS
If an animation is rendering:
- the autosave should properly be cancelled without stopping render
or
- the autosave should be temporary disabled before animation is rendered, and
enabled once rendering is done (if enable before rendering)
NOTES
- Maybe related to https://bugs.kde.org/show_bug.cgi?id=410024
- Discussion on krita-artists:
https://krita-artists.org/t/krita-5-animation-curves-applied-to-transform-mask/24895/13?u=grum999
Grum999
--
You are receiving this mail because:
You are watching all bug changes.
