GIMP crashed on closing, crash to gnome-vfs-module-callback.c: remove_one_stack()

[Prairie Aviation Brad]

Resized about 10 images then tried to close and GIMP crashed

[Sebastien Bacher (seb128)]

Thanks for your bug. That looks like a gnome-vfs crasher according to the backtrace:

(gdb) thread apply all bt

Thread 3 (process 7105):
#0 0xb344b128 in ?? () from /lib/libbz2.so.1.0
#1 0xb34579e0 in _fini () from /lib/libbz2.so.1.0
#2 0xb7f494ce in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#3 0xb7593299 in exit () from /lib/tls/i686/cmov/libc.so.6
#4 0x08063221 in ?? ()
#5 0x00000000 in ?? ()

Thread 2 (process 7490):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb750c131 in __lll_mutex_unlock_wake () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7508e4a in _L_mutex_unlock_269 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb7696ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#4 0x00000000 in ?? ()

Thread 1 (process 7489):
#0 IA__g_slist_foreach (list=0x31, func=0xb62dcc30 <callback_info_unref_func>, user_data=0x0) at gslist.c:467
#1 0xb62dcc7f in remove_one_stack (key=0x8bf3290, value=0x31, callback_data=0x0) at gnome-vfs-module-callback.c:363
#2 0xb7767b6a in g_hash_table_foreach_remove_or_steal (hash_table=0x8bd5d40, func=0xb62dcc40 <remove_one_stack>,
    user_data=0x0, notify=1) at ghash.c:605
#3 0xb62dcacc in clear_stack_table (stack_table=0x31) at gnome-vfs-module-callback.c:389
#4 0xb62dd22e in stack_table_destroy (specific=0x8bd5d40) at gnome-vfs-module-callback.c:417
#5 0xb7505d5c in __nptl_deallocate_tsd () from /lib/tls/i686/cmov/libpthread.so.0
#6 0xb7506512 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb763451e in clone () from /lib/tls/i686/cmov/libc.so.6

[Sebastien Bacher (seb128)]

I've forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=365647

[ricardisimo (ricardisimo)]

Similar situation: rotated and saved one image, then tried to close it and open the next for the same thing - crash.

[Thomas Hotz (thotz-deactivatedaccount)]

I saw from the GNOME Bugzilla report it might be a possible dup of 359655? Can a developer check this? Thank you!

[Thomas Hotz (thotz-deactivatedaccount)]

Marking this bug as invalid, because it is that old, but if somebody can reproduce this bug, I'll test it. Thank you very much for your patience.