app crashed after a few minutes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pinta |
New
|
Undecided
|
Unassigned |
Bug Description
installed Pinta on Debian 10 (buster) using:
https:/
Played a little with the mouse, draw some sketch and played with the filters.
All seemed fine until I tried opening a file, which caused a majestic crash
as reported below:
elias@dell15:
free(): invalid pointer
Stacktrace:
at <unknown> <0xffffffff>
at (wrapper managed-to-native) GLib.SList.g_free (intptr) [0x00002] in <5a439e0caae746
at GLib.ListBase.Empty () [0x000b5] in <5a439e0caae746
at GLib.ListBase.
at GLib.ListBase.
at (wrapper runtime-invoke) object.
/proc/self/maps:
40b05000-40b15000 rwxp 00000000 00:00 0
41aa9000-41b99000 rwxp 00000000 00:00 0
41bce000-41cae000 rwxp 00000000 00:00 0
55bb940ec000-
55bb94117000-
55bb9440d000-
55bb9453b000-
55bb94541000-
55bb94547000-
55bb95068000-
7fcc24bfa000-
7fcc24bfb000-
7fcc253fb000-
7fcc253fc000-
7fcc263fd000-
7fcc263fe000-
7fcc26bfe000-
7fcc26bff000-
7fcc273ff000-
7fcc27400000-
7fcc27e00000-
7fcc28000000-
7fcc28021000-
7fcc2c000000-
7fcc2c07e000-
Memory around native instruction pointer (0x7fcc786847bb):
0x7fcc786847ab d2 4c 89 ce bf 02 00 00 00 b8 0e 00 00 00 0f 05 .L..............
0x7fcc786847bb 48 8b 8c 24 08 01 00 00 64 48 33 0c 25 28 00 00 H..$....dH3.%(..
0x7fcc786847cb 00 44 89 c0 75 1d 48 81 c4 10 01 00 00 5b c3 66 .D..u.H......[.f
0x7fcc786847db 0f 1f 44 00 00 48 8b 15 89 36 18 00 f7 d8 64 89 ..D..H...6....d.
Native stacktrace:
/usr/bin/
/usr/bin/
/usr/bin/
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
[0x41c2e85d]
Pkilling 0x7fcc78648780 from 0x7fcc7593d700
Entering thread summarizer pause from 0x7fcc7593d700
Finished thread summarizer pause from 0x7fcc7593d700.
Waiting for dumping threads to resume
Debug info from gdb:
mono_gdb_
=======
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=======
Aborted
elias@dell15:
seems like this is consistent!
It happens almost immediately after I load an image file