I downloaded this program a couple of days ago after hearing good things about it.

Tried it out today and every single time I try to open a canvas, it crashes. Mind you, I'm not using a large file size. I tried 3400 x 2000 at first and maybe thought it was too big, but it keeps crashing at 1500 x 1000 which all the other drawing programs I have tried can handle perfectly.

I also thought perhaps it was too much for my PC when I had my display tablet set up, but it continues to crash on my laptop with no other programs open, or external devices connected.

Running most recent version on Windows 8

Super disappointed so far

Check first: https://docs.krita.org/KritaFAQ#Krita_s ... _Intel_GPU

If that isn't what is causing the crashes, make a backtrace and sent it to bugs.kde.org:
https://docs.krita.org/Dr._Mingw_debugger

Likely though, updating your graphics driver will solve the issue.

TheraHedwig wrote:Check first: https://docs.krita.org/KritaFAQ#Krita_s ... _Intel_GPU

If that isn't what is causing the crashes, make a backtrace and sent it to bugs.kde.org:
https://docs.krita.org/Dr._Mingw_debugger

Likely though, updating your graphics driver will solve the issue.

Unfortunately it wasn't that easy. How do I backtrace it? And will this help me or go unanswered in the sea of bug reports?

Well, if it isn't the opengl bug that thousands upon thousands of intel drivers are affected with, the information in the second link should tell you how to make a backtrace. Without the backtrace we cannot figure out where it is crashing in the code on your computer. Without the bug report, we cannot track if we fixed this particular bug.

So yes, you are right, making a backtrace and bugreport will not help against the crashes now, but not making them will mean we will never be able to even make the slightest attempt at fixing it. I am afraid that is all the help I can give you right now.

Edit: For what it's worth, crash reports do get priority over all other bugs and tend to be easy to fix, but we do need to know where in the code it is crashing first.

TheraHedwig wrote:Well, if it isn't the opengl bug that thousands upon thousands of intel drivers are affected with, the information in the second link should tell you how to make a backtrace. Without the backtrace we cannot figure out where it is crashing in the code on your computer. Without the bug report, we cannot track if we fixed this particular bug.

So yes, you are right, making a backtrace and bugreport will not help against the crashes now, but not making them will mean we will never be able to even make the slightest attempt at fixing it. I am afraid that is all the help I can give you right now.

Edit: For what it's worth, crash reports do get priority over all other bugs and tend to be easy to fix, but we do need to know where in the code it is crashing first.

I disabled the OpenGL and so far so good if anything else comes up I'll be back, but for now thanks for the help!