https://bugs.kde.org/show_bug.cgi?id=388495
--- Comment #4 from Linus Larsson <li...@riotamot.com> --- (In reply to Boudewijn Rempt from comment #3) > I have no idea how that's even possible... Perhaps the error message is misleading. KisUndoView appear to work with the history docker in Krita: https://searchcode.com/codesearch/view/19399478/ (KisUndoView.h) https://searchcode.com/codesearch/view/19399475/ (KisUndoView.cpp) I have a couple of uneducated guesses: - I've previously had hardware memory related issues, where my Nvidia driver appear to taint the kernel, thus have turned off hardware acceleration in Krita. Could this be hardware related as well; the undo stack is becoming corrupted? - The history docker extension is using deprecated indexing config from a previous Krita install? - Undo stack set too large; or another memory allocation user-side snafu? -- You are receiving this mail because: You are watching all bug changes.
