Bug 380436

Summary:	Adding a shape crashes the program
Product:	[Applications] krita	Reporter:	Aris <nektariosntasios>
Component:	Layers/Vector	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	freebox64, halla
Priority:	NOR
Version:	3.1.4
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Attachments:	GDB report Video example

Description Aris 2017-06-01 18:18:53 UTC

When i try to add a shape (an arrow or a rectangle or other) in a picture the program crashes down. Its closing without saving the work. The latest working version that i have tried is 3.1.2.1 64bit
3.1.3 and 3.1.4 is crashing!!!
Please, check it out.

Comment 1 mvowada 2017-06-03 07:21:24 UTC

Created attachment 105860 [details]
GDB report

I think I can confirm this behaviour on Ubuntu 14.04 with Krita 3.1.4 appimage.
Please, see the video example and the gdb report.

Comment 2 mvowada 2017-06-03 07:22:02 UTC

Created attachment 105861 [details]
Video example

Comment 3 mvowada 2017-06-03 07:26:19 UTC

( maybe similar to Bug 378328  )

Comment 4 mvowada 2017-06-05 16:11:42 UTC


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

Comment 5 Halla Rempt 2017-06-07 11:20:41 UTC

The problem with the backtrace is that it doesn't show anything inside krita, but allocating memory fails:


Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0x39f2bc1760 <main_arena>, bytes=56) at malloc.c:3302
3302	malloc.c: File o directory non esistente.

It doesn't give any clue :-(

Comment 6 Aris 2017-06-07 11:29:14 UTC

I am quiet sure that the same problem existed in some older versions. I had come on it and the solution was to go back to the previous version. So it was resolved once, why did it came up again?

Comment 7 Halla Rempt 2017-06-07 12:14:09 UTC

I haven't been able to reproduce this issue in any version of Krita, and I haven't seen something like this happen since 2.2 -- and I have never fixed any issue like this. So I cannot say that it was "resolved", and I cannot tell you why some people experience it...