https://bugs.kde.org/show_bug.cgi?id=455203
--- Comment #6 from gimmemyco...@protonmail.com --- Awesome, thanks for the very quick replies on this bug report! Sent with Proton Mail secure email. ------- Original Message ------- On Tuesday, June 14th, 2022 at 1:50 AM, Halla Rempt <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=455203 > > --- Comment #5 from Halla Rempt ha...@valdyas.org --- > > This is the relevant backtrace: > > > krita.exe caused an Access Violation at location 00007FFC19D3164F in module > libkritacommand.dll Reading from location FFFFFFFFFFFFFFFF. > > AddrPC Params > 00007FFC19D3164F 00000000132AAA00 000000000F1BFDA0 000000005184FB10 > libkritacommand.dll!0x164f KUndo2Command::actionText+0xf > 00007FFC19D319FF 01D6492054215D49 0000000000000001 0000000020DC8410 > libkritacommand.dll!0x19ff KUndo2QStack::undoText+0x5f > 00007FFC19D31B2F 000000000F1BFE70 000000006FD084C2 000000000000000E > libkritacommand.dll!0x1b2f KUndo2QStack::setIndex+0xbf > 00007FFC19D34412 0000000000000000 000000005184FB10 000000005172C810 > libkritacommand.dll!0x4412 KUndo2QStack::push+0x282 > 00007FFBB5346DCB 000000000CD37381 0000000000000000 0000000000000000 > libkritaimage.dll!0x116dcb > KisStrokeStrategyUndoCommandBased::finishStrokeCallback+0x10b > 00007FFBB5518FC4 0000000000000010 000000001CD95850 0000000051AAF8A0 > libkritaimage.dll!0x2e8fc4 KisUpdateJobItem::run+0x94 > 00007FFBAF308610 0000000051A9DDC0 0000000051AAF800 0000000000000000 > Qt5Core.dll!0x28610 QThreadPool::tryStart+0x520 > 00007FFBAF30162F 0000000000000000 0000000000000000 0000000000000000 > Qt5Core.dll!0x2162f QThread::qt_metacall+0x69f > 00007FFC1FD37BD4 0000000000000000 0000000000000000 0000000000000000 > KERNEL32.DLL!0x17bd4 BaseThreadInitThunk+0x14 > 00007FFC2136CE51 0000000000000000 0000000000000000 0000000000000000 > ntdll.dll!0x6ce51 RtlUserThreadStart+0x21 > > Since we fixed some issues in the undo stack for the upcoming Krita 5.1, > there's a fair chance you won't experience this issue when using the nightly > builds (though those might have other problems). > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
