pinta crashes with a mono error when trying to edit images

Bug #1686173 reported by Ted Crilly on 2017-04-25
This bug affects 13 people
Affects Status Importance Assigned to Milestone
pinta (Ubuntu)

Bug Description

After upgrading to 17.04, I noticed that pinta crashed all the time with issues related to mono. I thought maybe some library was not up to date and reinstalled pinta and mono, but no luck.

I have attached the stack trace to this report
*** Error in `/usr/bin/mono': free(): invalid pointer: 0x000055b5ef57ae60 ***
======= Backtrace: =========
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.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pinta (Ubuntu):
status: New → Confirmed

Interestingly, I can't get it to crash when I run `pinta` in a terminal. If I use the desktop launcher, however, it crashes if I try to do anything more than "save as."

For me the error starts when I press the OPEN FILE button (or inside the menu) on Pinta to open an image, it opens up and then the app crashes almost immediately. Instead, if I go direct to the image on directory and Right Click it selecting to open in Pinta, the app work as expected. Dragging the file inside the opened app will work as well.

Mike Holmes (mike-holmes) wrote :

Save fails for me, if start from the terminal I get

mike@mike-desktop:~$ pinta
*** Error in `/usr/bin/mono': double free or corruption (out): 0x000056419461d1b0 ***
======= Backtrace: =========

mborodin (m-borodin80) wrote :

When I open picture and try to select area, I'm getting the same error:

maxim@maxim-laptop:~$ pinta
*** Error in `/usr/bin/mono': free(): invalid pointer: 0x00007fae1c0012a0 ***
======= Backtrace: =========
======= Memory map: ========
4080c000-4081c000 rwxp 00000000 00:00 0
40c83000-40dc7000 rwxp 00000000 00:00 0

twdkeule (twdkeule) wrote :

I had a related issue ( and updating \Mono to 5.4.1 using their PPA ( resolved the issue.

Magnus Helander (mhelander) wrote :

Pinta 1.6 on Ubuntu 18.04.1
Pinta Crashed with *** Error in `/usr/bin/mono': free(): invalid pointer:
Followed #7 twdkeule and added Mono PPA, updated to
Mono JIT compiler version (tarball Mon Aug 6 09:07:45 UTC 2018)
Issues resolved - Pinta stable.

Fabian (fabianroeling) wrote :

The fix in the last version worked for me, using Debian 9.11 and Pinta 1.6. Can this then be closed and moved over to a Mono bug report? Or can it simply be closed, because the latest Mono version already fixes it?

Moritz Lenz (moritzlenz) wrote :
Download full text (7.4 KiB)

I just got a SIGSEGV from using pinta 1.6-2 the first time.

I opened two images, and used the rectangle select tool. Nothing more.

Dunno if this this is the same bug as previously reported:

 Native Crash Reporting
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

 Native stacktrace:
 0x5557e66e1eb5 - /usr/bin/mono : (null)
 0x5557e66e2250 - /usr/bin/mono : (null)
 0x5557e668f129 - /usr/bin/mono : (null)
 0x5557e66db9c1 - /usr/bin/mono : (null)
 0x7f29ee1d5d3e - /usr/lib/x86_64-linux-gnu/ : g_slice_free_chain_with_offset

 Telemetry Dumper:
Pkilling 0x7f29f25d7780 from 0x7f29f1eb7700
Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2)
Entering thread summarizer pause from 0x7f29f1eb7700
Finished thread summarizer pause from 0x7f29f1eb7700.

Waiting for dumping threads to resume

(Pinta:92051): GLib-CRITICAL **: 10:24:03.253: Source ID 1431 was not found when attempting to remove it

 External Debugger Dump:
[New LWP 92052]
[New LWP 92053]
[New LWP 92054]
[New LWP 92055]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".
0x00007f29ede61113 in ?? () from /usr/lib/x86_64-linux-gnu/
  Id Target Id Frame
* 1 Thread 0x7f29f25d7780 (LWP 92051) "mono" 0x00007f29ede61113 in ?? () from /usr/lib/x86_64-linux-gnu/
  2 Thread 0x7f29f17ff700 (LWP 92052) "SGen worker" futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5557e6ad3e08) at ../sysdeps/nptl/futex-internal.h:183
  3 Thread 0x7f29f1eb7700 (LWP 92053) "Finalizer" 0x00007f29f26c1dff in __GI___wait4 (pid=92109, stat_loc=0x7f29f1eb5d14, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
  4 Thread 0x7f29ed4da700 (LWP 92054) "gmain" 0x00007f29f26f1aff in __GI___poll (fds=0x5557e8141ce0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  5 Thread 0x7f29eccd9700 (LWP 92055) "gdbus" 0x00007f29f26f1aff in __GI___poll (fds=0x5557e814f460, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

Thread 5 (Thread 0x7f29eccd9700 (LWP 92055)):
#0 0x00007f29f26f1aff in __GI___poll (fds=0x5557e814f460, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007f29ee1b71ae in () at /usr/lib/x86_64-linux-gnu/
#2 0x00007f29ee1b7533 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/
#3 0x00007f29e...


Cameron White (cameronwhite91) wrote :

This looks like the same issue - could you try installing the latest version of Mono from

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Bug attachments