Bug 383309 – double free or corruption in gnome-screenshot

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 383309 - double free or corruption in gnome-screenshot


Summary:	double free or corruption in gnome-screenshot

Description Kjartan Maraas 2006-12-07 10:17:44 UTC

Backtrace:

(gdb) thread apply all bt

Thread 2 (Thread -1237709936 (LWP 22983))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libc.so.6
#2 _L_lock_41
from /lib/libc.so.6
#3 ptmalloc_lock_all
at arena.c line 254
#4 __libc_fork
at ../nptl/sysdeps/unix/sysv/linux/fork.c line 92
#5 __fork
at ../nptl/sysdeps/unix/sysv/linux/pt-fork.c line 26
#6 libgnomeui_segv_handle
at gnome-ui-init.c line 847
#7 <signal handler called>
#8 __kernel_vsyscall
#9 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#10 *__GI_abort
at abort.c line 88
#11 __libc_message
#12 _int_free
at malloc.c line 5774
#13 *__GI___libc_free
at malloc.c line 3552
#14 IA__g_free
at gmem.c line 187
#15 remove_one_stack
at gnome-vfs-module-callback.c line 362
#16 g_hash_table_foreach_remove_or_steal
at ghash.c line 605
#17 clear_stack_table
at gnome-vfs-module-callback.c line 389
#18 _gnome_vfs_module_callback_clear_stacks
at gnome-vfs-module-callback.c line 960
#19 _gnome_vfs_job_execute
at gnome-vfs-job.c line 1751
#20 thread_entry_point
at gnome-vfs-job-queue.c line 65
#21 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#22 g_thread_create_proxy
at gthread.c line 553
#23 start_thread
at pthread_create.c line 296
#24 clone
from /lib/libc.so.6

Comment 1 Emmanuele Bassi (:ebassi) 2006-12-07 10:37:17 UTC

I don't see any gnome-screenshot function in this stack trace; seems more like a gnome-vfs bug to me.

Comment 2 Kjartan Maraas 2006-12-08 14:22:11 UTC

Let's move it there then.

Comment 3 Kjartan Maraas 2007-01-08 10:53:24 UTC

Looks like it could really be a problem in at-spi from the backtrace in thread 1. I'll recheck and see if it's fixed already

Comment 4 Kjartan Maraas 2007-01-25 14:57:07 UTC

Can't reproduce this any more. Closing.