Bug 325462

Summary: Crash when closing the Document Information window with a tablet
Product: [Applications] krita Reporter: Eiko Yumi <esdouzewa>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: dimula73, halla
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Eiko Yumi 2013-09-30 13:57:54 UTC 
Using a pen stylus to close the document information window with the "window close" titlebar button [X] causes Krita to crash immediately, losing any unsaved work. By using a mouse this doesn't happen.

Build: Win-x64 2.7.8.18

Reproducible: Always

Steps to Reproduce:
1. Create a new image
2. File>Document Information
3. Click the [X] close windows button with a pen tablet
Actual Results:  
The program crashes.

Expected Results:  
The Document Information window should get safely closed.

Relevant output from Debugview when Krita crashes in that way:

[8024] CRITICAL: According to statistics of the KisTileDataStore some tiles have leaked from the Krita control! 
[8024] CRITICAL: Tiles in memory: 3 Total tiles: 3 
[8024] QWaitCondition: Destroyed while threads are still waiting
[8024] QWaitCondition: Destroyed while threads are still waiting
Comment 1 Halla Rempt 2013-09-30 14:10:27 UTC 
Bah... When I try that on my helix, I don't get a crash, so I cannot debug :-(
Comment 2 Eiko Yumi 2013-09-30 14:33:43 UTC 
I made a video showing the process:
https://www.youtube.com/watch?v=3YlJjHGlbOc
Comment 3 Eiko Yumi 2013-10-07 00:42:05 UTC 
I found out that the same behavior happens on all non-OS native window dialogs on the build of Krita I'm using. Still only when I use my Wacom pen tablet, though.
Comment 4 Halla Rempt 2013-10-08 07:54:57 UTC 
Ah, right -- this is the wacom wintag build, right? There it's reproducible.
Comment 5 Eiko Yumi 2013-10-08 09:03:21 UTC 
It is. This also happens on build 2.7.8.21.
Comment 6 Dmitry Kazakov 2013-11-30 09:36:39 UTC 
I guess this bug has already been fixed. I've just checked 2.7.8.29 and it works ok here.