Steps to reproduce:
1. start gthumb
2. select some folder
3. rename
4. gthumb terminates (segmentation fault)


Stack trace:


Other information:
gthumb version 2.10.6 from Ubuntu Hardy repositories
I cannot reproduce the error in a deterministic way, but it happens frequently
Even if it doesn't crash, valgrind reports lost memory:
hph@hackbrett:~$ valgrind gthumb
...
==13487== ERROR SUMMARY: 85 errors from 34 contexts (suppressed: 267 from 2)
==13487== malloc/free: in use at exit: 10,006,658 bytes in 70,791 blocks.
==13487== malloc/free: 765,748 allocs, 694,957 frees, 147,076,400 bytes allocated.
==13487== For counts of detected errors, rerun with: -v
==13487== searching for pointers to 70,791 not-freed blocks.
==13487== checked 10,847,540 bytes.
==13487== 
==13487== LEAK SUMMARY:
==13487==    definitely lost: 138,093 bytes in 4,822 blocks.
==13487==      possibly lost: 412,071 bytes in 456 blocks.
==13487==    still reachable: 9,456,494 bytes in 65,513 blocks.
==13487==         suppressed: 0 bytes in 0 blocks.