so far i have tried uninstalling/reinstalling, trying the newest update, restarting my computer etc. in task manager it briefly appears as a background task then disappears again
i have a crash report but i dont know how to read them
Dude… Pastebin or a .txt, please…
1 Like
One can alternatively put code in the Preformatted Text encoding, shortcut is CTRL + E, so select the text to format and either click the button </> in the editor toolbar which does the same or use the above shortcut CTRL + E. And if you want to manually format such long code passages, you have to put it in three backticks in the line before the beginning ``` and after the end of such a passage of text.
Michelist
This crash report doesn’t have a backtrace. Is there a crash log in %LOCALAPPDATA%\kritacrash.log?
sorry ive never used this site before!! my bad!
so, i somehow fixed the problem yesterday and im not sure how. annoyingly, im now having the exact same issue.
here’s the crash from yesterday: -------------------Error occurred on Wednesday, March 25, 2026 at 22:47:56. - Pastebin.com it isnt giving me one for the issues today, for some reason, but im hoping it will help solve a reoccurring problem?
update: i found a really strange fix. i went through every method i found online (restarting my pc, changing the kritarc file to kritarc_old and reloading, even deleting an oversized krita.log file when nothing else worked) and NOTHING. In my research i found out that it could be my AMD drivers which I remembered recently updated, and it WAS!
the only way to get Krita to load is to disable my AMD driver, load up Krita without it (it will crash), enable my AMD driver again then load up Krita a second time.
posting this update in case anyone else comes across the same problem I had and isn’t able to fix it.
First crash in the log is when drawing the color sampler.
Summarized,
KisAsyncColorSamplerHelper::paintRectangle -> QPainter::drawPixmap -> QOpenGl2PaintEngineEx::drawPixmap -> ... -> libGLESv2.dll rx::VertexBufferInterface::getBufferSize -> null
Then there’s two crashes involving keyboard shortcut modifiers, which seem to happen on startup.
Summarized,
KisPart::createMainWindow -> ... -> KisInputManager::Private::fixShortcutMatcherModifiersState -> KistoolInvocationAction::processUnhandledEvent -> KisInputManager::toolProxy -> null