Bug 343515

Summary: Crash on close with backtrace 3 stars (Krita 2.9 Beta 2 (git 74993bf))
Product: [Applications] krita Reporter: mvowada <freebox64>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: halla
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Crash on close with backtrace 3 stars - BACKTRACE

Description mvowada 2015-01-29 12:33:48 UTC
I'm on Ubuntu 14.04 Unity, Krita 2.9 Beta 2 (git 74993bf), I stumbled on a crash on exit Krita and since the backtrace is flagged with 3 stars I thought to share it. Hope it makes sense.

(See backtrace in comment below)

Reproducible: Sometimes
Comment 1 mvowada 2015-01-29 12:34:16 UTC
Created attachment 90779 [details]
Crash on close with backtrace 3 stars - BACKTRACE
Comment 2 Halla Rempt 2015-01-29 12:36:36 UTC
Hm... What where you doing when you closed Krita? Which tool was active?
Comment 3 mvowada 2015-01-29 13:05:29 UTC
I'm sorry, unfortunately I can't remember the active tool at exit... 

I'm recalling what I did. Please, consider that I'm not completely sure these have been the only actions. And in fact it seems I'm not able to reproduce the crash by following these ones:

1. I opened a kra file with multiple layers (rasters and vectors)
2. I went on Layer > Import/Export > Import Layer... to import a previously saved Group layer (as .kra file)
3. I did some R+Click over canvas to select both the imported layer, the canvas background and again the imported layer
4. I switched to the "Transform a layer or a selection" tool and I shifted the imported layer over center > Apply
5. Flatten Image
6. I switched to the "Crop the image to an area" tool, set fixed ratio to 1.78, clicked and dragged the handles of the box to adjust the crop area > Crop Image
7. I exported as jpeg
8. I closed the document, without saving
9. And I closed Krita
Comment 4 Halla Rempt 2015-02-03 08:04:12 UTC

*** This bug has been marked as a duplicate of bug 343719 ***