Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 12189 bytes cmdline: geeqie comment: I've copied images from my camera to the PC in shell. Then I started geeqie and jumped back to the shell. In the shell I started renaming the JPG pictures, also moved the RAW images to another directory and then switched back to geeqie. geeqie crashed whilte rename was still running. component: geeqie Attached file: coredump, 22904832 bytes crash_function: file_data_unref_debug executable: /usr/bin/geeqie kernel: 2.6.35.14-97.fc14.x86_64 package: geeqie-1.0-11.fc14 rating: 4 reason: Process /usr/bin/geeqie was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1318768933 uid: 500 How to reproduce ----- 1. load some images from SD card to some directory 2. start geeqie and open that directory 3. start renaming and moving images in the directory
Created attachment 528386 [details] File: backtrace
So, this is still around. As mentioned before, it is not easily reproducible. One can rename/move/delete thousands of files with an external shell/tool, and Geeqie may survive that. The crash due to the assertion just means that filelist_free() ran into already freed filedata or invalid/corrupted memory. It does not tell in which place the filedata was freed before due to refcounting spread throughout the code. *** This bug has been marked as a duplicate of bug 655610 ***