Bug 332689 – gimp-gap crashes when duplicating frame

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 332689 - gimp-gap crashes when duplicating frame


Summary:	gimp-gap crashes when duplicating frame


Status:	RESOLVED FIXED

Product:	gimp-gap
Classification:	Other
Component:	video menu
Version:	2.2.0
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	hof
QA Contact:	hof

URL:
Whiteboard:

Duplicates:	341781 (view as bug list)
Depends on:
Blocks:

Reported:	2006-02-26 23:17 UTC by Sebastien Bacher
Modified:	2006-05-16 12:25 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Sebastien Bacher 2006-02-26 23:17:12 UTC

That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gimp-gap/+bug/32900/

"GIMP gives an error when duplicating the frame:
<Start of Error Message>
GIMP Message

Plug-In crashed: "gap_plugins"
(/usr/lib/gimp/2.0/plug-ins/gap_plugins)

The dying Plug-In may have messed up GIMP's internal state. You may want to save your images and restart GIMP to be on the safe side.

<End of Error Message>

I have restarted GIMP three times, two no avail, and tries reinstalling gimp-gap threw adept.

gdb of gimp

(gdb) exec-file gimp
(gdb)
(gdb) run gimp
Starting program: /usr/bin/gimp gimp
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 2003035840 (LWP 8520)]
*** glibc detected *** free(): invalid pointer: 0x08109180 ***

Program exited normally.
(gdb)"

Comment 1 Sebastien Bacher 2006-02-26 23:17:28 UTC

Backtrace of the issue:

Program received signal SIGABRT, Aborted.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt

+ Trace 66540

#0 __kernel_vsyscall
#1 raise
from /lib/tls/i686/cmov/libc.so.6
#2 abort
from /lib/tls/i686/cmov/libc.so.6
#3 __libc_message
from /lib/tls/i686/cmov/libc.so.6
#4 _int_free
from /lib/tls/i686/cmov/libc.so.6
#5 free
from /lib/tls/i686/cmov/libc.so.6
#6 IA__g_free
at gmem.c line 187
#7 p_copy_png_thumb
at gap_thumbnail.c line 298
#8 gap_thumb_file_copy_thumbnail
at gap_thumbnail.c line 484
#9 gap_lib_image_file_copy
at gap_lib.c line 768
#10 p_dup
at gap_base_ops.c line 627
#11 gap_base_dup
at gap_base_ops.c line 1486
#12 run
at gap_main.c line 1387
#13 gimp_main
from /usr/lib/libgimp-2.0.so.0
#14 main
at gap_main.c line 621

Comment 2 Carol 2006-02-27 23:14:03 UTC

I am using gimp from a recent cvs update along with a fresh update of gimp-gap and all of this with the glib and gtk+ and supporting softwares from debian sid -- i am unable to reproduce this gimp or gimp-gap crash.

I can also say that I never had this problem in all of the many years and many combinations of debian gtk+, glib and cvs gimp cvs gimp-gaps I have been using since September 2004.  Quite often, this combination of software has been used by me extensively and even ignorantly (like it was stable enough for me to learn with....)

How difficult is it to find a diff between the two very similar distributions of the software that is being used?

Comment 3 Sebastien Bacher 2006-02-28 16:57:22 UTC

Ubuntu has gimp-gap 2.2.0-2 (same package as Debian), gimp 2.2.10 (only little change from Debian), gtk 2.8.13, glib 2.10.0

Comment 4 hof 2006-03-09 11:14:42 UTC

made an attempt to fix this bug in the current CVS version.
(The bug was not reproduceable with gtk 2.6.x, tests
with gtk 2.8.13 were not yet performed)

The fix uses g_object_unref to free GimpThumbnail objects instead
of g_free (that may cause problems in other gtk version)

Turning off thumbnail saving via preferences could be a temporary workaround if the problem still exist in your environment.

Comment 5 Sebastien Bacher 2006-03-12 17:25:25 UTC

That fixes the crash

Comment 6 hof 2006-05-16 12:25:45 UTC

*** Bug 341781 has been marked as a duplicate of this bug. ***