Bug 382672 - Krita Crash
Summary: Krita Crash
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: krita
Classification: Applications
Component: Usability (other bugs)
Version First Reported In: 3.1.4
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 18:36 UTC by Patrick Watson
Modified: 2018-05-20 20:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Log generated by Krita on Crash (8.25 KB, text/plain)
2017-07-24 18:36 UTC, Patrick Watson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Watson 2017-07-24 18:36:39 UTC
Created attachment 106835 [details]
Log generated by Krita on Crash

Here is the log attached, I tabbed back into Krita after watching Youtube and Krita froze then crashed. PC Specs are as followed:
Intel Core I7 4770k @ 4.2Ghz (Completely stable)
Asus Z97-P
16Gb DDR3 1600Mhz (4x4Gb)
RX 480 4GB Gigabyte G1 Gaming
Windows 10 Pro 64 Bit.
Wacom Intuos Pro Med
All drivers are up-to-date.
Comment 1 Halla Rempt 2017-07-27 08:48:42 UTC
Hi Patrick,

I wonder whether you can reproduce this issue. I doubt it really has something to do with watching youtube, from the backtrace it looks like Krita tried to finish some action and add it to the undo stack after the image it was working on had been deleted. But if it's not reproducible, it's going to be very hard to fix :-(
Comment 2 Patrick Watson 2017-07-27 14:27:41 UTC
If I can come across it again I shall update this thread with what I did, I was working on a pretty big canvas (Over 6000x6000) so it might have something to do with that.
Comment 3 Halla Rempt 2017-08-18 14:09:58 UTC
Okay, let's wait for that.
Comment 4 Raghavendra kamath 2018-05-20 20:46:07 UTC
Hi Patrick,

Can you check the latest version of krita and see if you can reproduce this bug.

For now I am going to close this bug report, if you think you can reproduce this please feel free to open this bug report again.

thank you