Bug 378573

Summary:	Group not editable
Product:	[Applications] krita	Reporter:	Adam Earle <MrAdamEarle>
Component:	Animation	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dimula73, halla
Priority:	NOR
Version First Reported In:	3.1.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Adam Earle 2017-04-09 01:17:06 UTC

Group not editable

This only seems to happen when I drawing at a 6k to 8 k range for print. krita gets really funky and does weird stuff all the time operating at this level which makes it crash all the time as well considering of 32 gigs of ram and a GTX 960

Also it seems to happen when I have multiple windows open for Krita for scripts breakdowns and reference.

an option to open the current document in a new view would be awesome so you could mirror it and view its mirrored version update in real time.

to be honest, I am not sure if I am really pushing Krita's boundaries because I am operating at such a high print resolution. I am using animations as pages in a book conceptually  so each new frame i like turning the page

Thanks guys

Comment 1 Halla Rempt 2017-04-11 07:55:22 UTC

Hi Adam,

I've seen this happen, too. I'm still not sure what causes it. You selected the "Animation" component -- is that correct, do you think it has to do with working with animations? We did fix a lot of animation related issues in 3.1.3 beta 1, so you could give that a try instead of 3.1.1.

I'm working usually with 6000x4000 images and a score or so of layers myself on a 16gb machine, and I never get a crash... I also use multiple windows when working at my desk on another machine. If you get frequent crashes, please follow https://docs.krita.org/Dr._Mingw_debugger so we can have a crash log to look at. 

You can open a document in a new view -- windows/new view/your document.

Comment 2 Dmitry Kazakov 2017-04-30 13:37:26 UTC

The bug should now be fixed. Please update to 3.1.3 RC1. The bug should no longer appear.

Fixing commit:
https://commits.kde.org/krita/9c57c307302e224edebd87413e86058503205311