When I am painting, Krita randomly crashes, and my work is always gone. By doing the slightest bit of movement can cause it to crash. My work is always getting lost, which means every 2 minutes into painting, I have to constantly save so if it do crashes, I can at least have a bit of my painting back, and when I do open it, Krita merges ALL my layers together, which makes it REALLY frustrating. Reproducible: Always Steps to Reproduce: 1.Open up Krita and start painting for a good amount of time 2. Out of nowhere, my brush turns into a blue, circles, resembling the ones you get when you click on too many things on a computer 3. A message pops up saying there is something wrong with krita, then it closes Actual Results: I have not tried to reproduced those steps in fear my work will be deleted. Expected Results: The software shouldn't have to crash, randomly oh so often, but if it did, there should have been a way to get your image AND your layers back. SEPERATLELY I'm starting to regret updating krita, The previous version worked effortlessly.
Hi Ednie, Thanks for your report. This behavious is not normal: most users do not experience this. Could you attach a screenshot of the error message popup? "A message popups saying there is something wrong" doesn't tell me a whole lot. Are you using a drawing tablet? If so, and if it isn't a wacom, could you check the builds from https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-vector-art-awesome/posts/1594853 Could you also check whether the debug build at http://www.valdyas.org/~boud/krita-3.0-d4fed25-x64-dbg.zip gives useful information when a crash happens? You have to run debugview to see the output. Finally, it seems some people have problems with Windows 10 updates: https://forum.kde.org/viewtopic.php?f=139&t=133516&p=358884#p358876
Created attachment 99692 [details] attachment-13391-0.html Sending you a picture of the pop up is going to be a problem because right after I filed a report, I uninstalled Krita. I was fed up with the bug and I didn't want to lose anymore of my work. On Jun 24, 2016 2:14 AM, "Boudewijn Rempt via KDE Bugzilla" < bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=364688 Boudewijn Rempt <boud@valdyas.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |boud@valdyas.org Platform|Windows CE |MS Windows OS|Windows CE |MS Windows --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> --- Hi Ednie, Thanks for your report. This behavious is not normal: most users do not experience this. Could you attach a screenshot of the error message popup? "A message popups saying there is something wrong" doesn't tell me a whole lot. Are you using a drawing tablet? If so, and if it isn't a wacom, could you check the builds from https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-vector-art-awesome/posts/1594853 Could you also check whether the debug build at http://www.valdyas.org/~boud/krita-3.0-d4fed25-x64-dbg.zip gives useful information when a crash happens? You have to run debugview to see the output. Finally, it seems some people have problems with Windows 10 updates: https://forum.kde.org/viewtopic.php?f=139&t=133516&p=358884#p358876 -- You are receiving this mail because: You reported the bug.
Created attachment 99694 [details] 20160625_184104.jpg I decided to give Krita another tried and after a couple of minutes into using it, the same message pup up, not only that, but its also lagging really badly.
I've had reports like this from two or three other Windows users, and I am at a loss to figure out what's up. It's obviously exceptional, otherwise I would have been able to reproduce it. Can you give us some details about your system, and check whether the crashes also happen if you disable opengl in settings/configure krita/display? * cpu and amount of memory * graphics card and driver version * tablet brand and driver version Do you have any antivirus software such as sandboxie or norton installed?
I'm sorry, but we cannot do anything else with this report. The behaviour is not normal and almost certainly caused by something specific to your system. What that is, is important to determine from a distance.