Bug 396688 - Program crashes on rotating canvas.
Summary: Program crashes on rotating canvas.
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: OpenGL Canvas (show other bugs)
Version: 4.1.1
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-20 12:24 UTC by oskar.e.berglund
Modified: 2019-04-05 13:48 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
VS 2017 Debug output (90.35 KB, text/plain)
2018-07-26 07:23 UTC, oskar.e.berglund
Details

Note You need to log in before you can comment on or make changes to this bug.
Description oskar.e.berglund 2018-07-20 12:24:18 UTC
Rotating the canvas using the modifier keys shortcuts causes the program to crash. Trying to rotate once then rotating a few more times and the applicatation breaks. 

Tried using both CPU and GPU Canvas. Both crashes.

Using a Laptop: Lenovo Thinkpad S1 with Intel(R) HD Graphics.

CPU: i5-4300U
GPU: Intel® HD Graphics 4400
RAM: 8GB
HDD: SSD 128GB
OS: Windows 8.1

Screen is Wacom EMR compliant FHD.
Comment 1 Halla Rempt 2018-07-20 13:11:33 UTC
Hi Oskar,

I'm sorry, I cannot reproduce that on my Lenovo Yoga 920.

* Could you please also attach the output of help->system information for bug reports?
* Could you follow the instructions on this page and provide a crash log? https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw
Comment 2 Alvin Wong 2018-07-26 06:36:57 UTC
Waiting for more info.
Comment 3 oskar.e.berglund 2018-07-26 07:23:32 UTC
Created attachment 114135 [details]
VS 2017 Debug output

Visual Studio 2017 Debug output for crashed Krita session.
New image created (1920x1080)

One Brush stroke made.
Rotated canvas.
Tried sampling a color with Alt-shortcut.
Application locks.
Comment 4 oskar.e.berglund 2018-07-26 07:26:09 UTC
Hi! Sorry for being so slow.

More information:

More specifically it happens when rotating the canvas with the Shift+Space shortcut (not when snapped rotating I think) and then trying to do something between each rotate like color picking or painting with a brush. I could record a video if you'd like?

Only crash log i found was from almost a year back from a older version so it's not relevant. Doesn't seem to get generated and the application must be forcefully closed.

I did try to do a debug using Visual Studio 2017 but haven't got a clue where to start doing it properly as I haven't used it before. I'm posting the debug output as an attachment.

System information:

Krita
  Version: 4.1.1

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.3.9600
  Pretty Productname: Windows 8.1 (6.3)
  Product Type: windows
  Product Version: 8.1

OpenGL Info
  **OpenGL not initialized**
Comment 5 Alvin Wong 2018-07-26 09:49:08 UTC
So it's a lock-up, not a crash. You won't get any crash logs if you just kill the process. You'll have to pause/break the process, find the thread that's stuck (probably the GUI thread) and get multiple stack traces to even have a chance to get some info that might help figuring out the issue.

I can't reproduce the freeze. I tried painting strokes, rotating the canvas and picking colours but nothing weird happened. Both with OpenGL canvas on and off.

(This bug report reminds me of bug 396179, but I can't tell if there are related at all...)
Comment 6 oskar.e.berglund 2018-07-26 12:29:19 UTC
I am able to reproduce it on a completely different machine with a fresh install.

CPU: i7-2600K
GPU: GTX 780 Nvidia
RAM: 32GB
HDD: SSD 512GB
OS: Windows 7

System information:

Krita
  Version: 4.1.1

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.1.7601
  Pretty Productname: Windows 7 SP 1 (6.1)
  Product Type: windows
  Product Version: 7sp1

OpenGL Info
  **OpenGL not initialized**


This is a stack for the thread that holds Krita at lock-up.

ntoskrnl.exe!memset+0x61a
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbd0
ntoskrnl.exe!PoStartNextPowerIrp+0x186d
ntoskrnl.exe!PoStartNextPowerIrp+0x1ae7
libkritaimage.dll!ZN17KisUpdaterContext14hasSpareThreadEv+0x1c
libkritaimage.dll!ZN15KisStrokesQueue12processQueueER17KisUpdaterContextb+0x4a
libkritaimage.dll!ZN18KisUpdateScheduler13processQueuesEv+0xbd
libkritaimage.dll!ZN18KisUpdateScheduler11barrierLockEv+0x23
libkritaimage.dll!ZN8KisImage11barrierLockEb+0x46
libkritaui.dll!ZN18KisAnimationPlayer11uploadFrameEi+0x1e1
Qt5Core.dll!ZN11QMetaObject8activateEP7QObjectiiPPv+0x7fa
Qt5Core.dll!ZN6QTimer10timerEventEP11QTimerEvent+0x5a
Qt5Core.dll!ZN7QObject5eventEP6QEvent+0x7b
Qt5Widgets.dll!ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c
Qt5Widgets.dll!ZN12QApplication6notifyEP7QObjectP6QEvent+0x2f0
libkritaui.dll!ZN14KisApplication6notifyEP7QObjectP6QEvent+0x16
Qt5Core.dll!ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x198
Qt5Core.dll!ZN28QEventDispatcherWin32Private14sendTimerEventEi+0xd9
Qt5Core.dll!ZN28QEventDispatcherWin32Private14sendTimerEventEi+0x5a3
USER32.dll!TranslateMessageEx+0x29d
USER32.dll!TranslateMessage+0x1e2
Qt5Core.dll!ZN21QEventDispatcherWin3213processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5cb
qwindows.dll!qt_plugin_instance+0x28e5
Qt5Core.dll!ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x13f
Qt5Core.dll!ZN16QCoreApplication4execEv+0x77
krita.exe+0x6641
krita.exe+0x13f7
krita.exe+0x14fb
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21
Comment 7 oskar.e.berglund 2018-07-26 12:31:24 UTC
Note that it never happened in 4.0.4 and prior. It only started occuring in 4.1.0 and 4.1.1.
Comment 8 Halla Rempt 2018-09-01 13:11:45 UTC
Meh... I still cannot reproduce this.
Comment 9 Jaime Torres 2018-10-01 13:45:02 UTC
Hello,

  Do you have, in Settings->Configure Krita->Display:
Canvas Graphics Acceleration enabled?
with Use texture buffer enabled?
with what scaling mode?

  Can you reproduce the crash/lock after disabling Use texture buffer or after disabling Canvas Graphics Acceleration (and the corresponding krita restart)?

  I can't reproduce neither the crash nor the lock with an Intel HD Graphics 4200, but I can reproduce something similar in https://bugs.kde.org/show_bug.cgi?id=399279

Best Regards.
Comment 10 oskar.e.berglund 2018-10-06 14:44:52 UTC
Hi, it happens on at least these changeable settings. Haven't tried every single combination. This is on the latest 4.1.3 version.

Canvas Graphics Acceleration off: Crash
Canvas Graphics Acceleration on (Auto OpenGL) - Nearest Neighbor Texture Buffer On: Crash
CGA Auto -  Bilinear Filtering - Texture Buffer On: Crash
CGA Auto -  Bilinear Filtering - Texture Buffer Off: Crash

CGA OpenGl - Nearest Neighbor - Texture Buffer On: Crash
CGA OpenGl - Nearest Neighbor - Texture Buffer Off: Crash
CGA OpenGl - Bilinear Filtering - Texture Buffer On: Crash
CGA OpenGl - Bilinear Filtering - Texture Buffer Off: Crash

CGA Direct3D - Nearest Neighbor - Texture Buffer On: Crash
CGA Direct3D - Nearest Neighbor - Texture Buffer Off: Crash
CGA Direct3D - Bilinear Filtering - Texture Buffer On: Crash
CGA Direct3D - Bilinear Filtering - Texture Buffer Off: Crash
Comment 11 Halla Rempt 2018-10-06 18:25:52 UTC
Hi Oskar,

I'm sorry, but I haven't got a single system where I can reproduce this issue. I have to admit that I cannot test on Win7 or Win8 anymore, since I no longer access to those operating systems.
Comment 12 oskar.e.berglund 2018-12-16 19:01:21 UTC
Hey!
It crashed on another system too, what they had in common was previous installs of Krita. Saw another bug where crashes happened sporadically but creating a fresh windows user seemed to solve it. 

So I tried just that and  it worked. So something with the user settings was not working with the newer versions. I can make some further investigations to try to find out which file or what is causing it depending on how my free time I have.

But clearing all local data for Krita and letting it have a fresh install makes it useable again in later versions it seems. Pretty weird!
Comment 13 Halla Rempt 2019-01-15 11:17:46 UTC
do you have a copy of the kritarc file that would provoke the crash?
Comment 14 Scott Petrovic 2019-03-30 12:55:54 UTC
Oskar...would it be possible to get a kritarc configuration file for this to see what might be happening. 

This ticket hasn't been looked at in a few months...so we can probably close it for now if we can't get a kritarc file
Comment 15 Scott Petrovic 2019-04-05 13:48:13 UTC
This issue is a bit old and and I think we narrowed it down to cleaning the kritarc file...which is the fix for a lot of things when versions get upgraded.

I am closing this for now. If an issue comes up again, you can file a new ticket and we can go from there.