https://bugs.kde.org/show_bug.cgi?id=446320
--- Comment #3 from Know Zero <knowz...@pokemail.net> --- (In reply to Know Zero from comment #1) > (In reply to Halla Rempt from comment #0) > > a81d83d340ea0fa0fcee652963faf262b92a07c3 > > > > After rendering to GIF, krita asserts: > > > > krita(2144656)/(default) kis_assert_common: ASSERT (krita): "m_process == > > nullptr" in file > > /home/halla/dev/krita/libs/ui/animation/KisFFMpegWrapper.cpp, line 47 > > > > See > > https://krita-artists.org/t/krita-next-crashes-when-rendering-animations-as- > > gif/32651 > > When gif is created, it is done in 2 parts. First to generate the palette. > Then using the palette to generate the final file. thus it fails the > m_process == nullptr as the pointer still holds the last process. > > Adding m_process.reset() > > after > > 158 if (processResults->finish == true) { > > should fix it. Looking at: https://bugs.kde.org/show_bug.cgi?id=442578 It seems the goal was to prevent manually doing the cleanup. If that is the case, other options include creating a separate FFMpegWrapper to run the palette, or merge the palettegen and paletteuse into 1 command. -- You are receiving this mail because: You are watching all bug changes.
