Bug 363755

Summary:	Moving a Saturation layer crashes
Product:	[Applications] krita	Reporter:	jalmiart
Component:	Layer Stack	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	halla, jalmiart, scottpetrovic
Priority:	NOR
Version First Reported In:	3.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jalmiart 2016-05-31 17:44:06 UTC

Moving a Saturation layer by dragging crashes Krita. See Steps to reproduce.

Reproducible: Always

Steps to Reproduce:
1. Create new custom document: Predefined A3, 300ppi, landscape, name it. On content tab, set 3 layers, with medium grey bg color. Other settings with default values.
2. Add some new layers, name them.
3. Fill one of the layers with black color and set its layer Blending Mode to Saturation.
4. Try to grag the layer to be topmost. If this does not yet cause crash, drag the layer somewhere once or twice again.

Actual Results:
UI becomes laggy/unresponsive, processor usage goes up from 5% to around 30% and memory usage from 35% to 95% and over. UI goes greyed out and soon "Krita has stopped working" dialog appears.

Expected Results:
The layer is moved without too much lagginess. Software does not crash.

Windows 7 Professional SP 1 64-bit
Intel Core i7-4712MQ CPU @2.30GHz
8,00 GB RAM
NVIDIA GeForce GT 740M

In Krita's performance settings, memory limit is set to 50% (all at default settings). Tried to reproduce 4 times, always crashed.

Problem signature:
Problem Event Name: APPCRASH
Application Name: krita.exe
Application Version: 0.0.0.0
Application Timestamp: 00000409
Fault Module Name: libkritaimage.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 6f808060
Exception Code: c0000005
Exception Offset: 000000000014e990
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1035
Additional Information 1: 82db
Additional Information 2: 82db4fd4bbdfe684fa3453fcfce68442
Additional Information 3: f8a3
Additional Information 4: f8a3a304453e7c46f9b9bbf9a29eef78

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Comment 1 Halla Rempt 2016-07-06 12:00:24 UTC

Hi Miia,

Thanks for your report. I haven't yet been able to reproduce the issue, I'm afraid.

Comment 2 Scott Petrovic 2016-07-13 14:06:01 UTC

I am having a hard time reproducing this too. Mila - Can you get this bug to happen on another computer? It is possible that it is specific to the Surface Pro 1.

Comment 3 Halla Rempt 2016-08-17 08:31:49 UTC

I think this was a generic timing error when d&d'ing layers in the layerbox: Dmitry has fixed that and the 3.0.1 development builds should be fine.

Comment 4 jalmiart 2016-08-20 11:50:49 UTC

Hi Boudewijn, 
Glad to hear if this helped to fix something. I thought this too was related to my mobile GPU like the other issue I reported. I did try it with every other layer mode, but only Saturation caused crash. I tested it now (very briefly) with krita-3.0.1-Alpha-ef558bb and it seems not occur any more. 

Sorry Scott, for some reason I had missed any notification about your question! Unfortunately I can currently only test Krita on this pc (which is not Surface Pro btw but Lenovo Thinkpad).