GNOME Bugzilla – Bug 397775
Crash while importing photos
Last modified: 2008-06-08 12:12:51 UTC
Steps to reproduce: 1. Import a large collection of photos 2. F-spot scans the entries 3. Segfault in mono Stack trace: [snip] Scanning /home/steveb/Pictures/iPhoto Library/Albums/Tahoe Trip Scanning /home/steveb/Pictures/iPhoto Library/Albums/To develop Scanning /home/steveb/Pictures/iPhoto Library/Desktop Scanning /home/steveb/Pictures/jacob's pictures disc Scanning /home/steveb/Pictures/jacob's pictures disc/By Me Scanning /home/steveb/Pictures/panos Scanning /home/steveb/Pictures/random pcs not in iphoto item changed open uri = file:///home/steveb/Pictures/DSC00023.JPG open uri = file:///home/steveb/Pictures/DSC00023.JPG open uri = file:///home/steveb/Pictures/DSC00023.JPG open uri = file:///home/steveb/Pictures/DSC00023.JPG Stacktrace: Native stacktrace: f-spot [0x8162eba] f-spot [0x812cd48] [0x37a440] f-spot [0x811b854] f-spot(mono_code_manager_destroy+0x22) [0x811b8c2] f-spot [0x812da66] f-spot [0x80dad0f] f-spot [0x809bfcd] f-spot [0x80976f1] f-spot [0x8121eb1] f-spot [0x80978d9] f-spot [0x80916e4] f-spot [0x8100532] f-spot [0x811e047] /lib/libpthread.so.0 [0x7932db] /lib/libc.so.6(clone+0x5e) [0x6d824e] item changed open uri = file:///home/steveb/Pictures/DSC00023.JPG open uri = file:///home/steveb/Pictures/DSC00023.JPG open uri = file:///home/steveb/Pictures/IMG_4491.JPG open uri = file:///home/steveb/Pictures/IMG_4491.JPG open uri = file:///home/steveb/Pictures/IMG_4491.JPG open uri = file:///home/steveb/Pictures/IMG_4491.JPG open uri = file:///home/steveb/Pictures/IMG_5296.JPG System.NullReferenceException: Object reference not set to an instance of an object at FSpot.JpegFile.get_Date () [0x00000] System.NullReferenceException: Object reference not set to an instance of an object at FSpot.JpegFile.get_Description () [0x00000] open uri = file:///home/steveb/Pictures/IMG_5296.JPG open uri = file:///home/steveb/Pictures/IMG_5296.JPG error checking orientation open uri = file:///home/steveb/Pictures/IMG_5296.JPG open uri = file:///home/steveb/Pictures/IMG_5326.JPG open uri = file:///home/steveb/Pictures/IMG_5326.JPG Debug info from gdb: (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208637728 (LWP 23539)] [New Thread -1248437360 (LWP 23548)] [New Thread -1242924144 (LWP 23543)] [New Thread -1241871472 (LWP 23542)] [New Thread -1219982448 (LWP 23541)] [New Thread -1219966064 (LWP 23540)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00795246 in pthread_mutex_lock () from /lib/libpthread.so.0 6 Thread -1219966064 (LWP 23540) 0x0037a402 in __kernel_vsyscall () 5 Thread -1219982448 (LWP 23541) 0x0037a402 in __kernel_vsyscall () 4 Thread -1241871472 (LWP 23542) 0x0037a402 in __kernel_vsyscall () 3 Thread -1242924144 (LWP 23543) 0x0037a402 in __kernel_vsyscall () 2 Thread -1248437360 (LWP 23548) 0x0037a402 in __kernel_vsyscall () 1 Thread -1208637728 (LWP 23539) 0x00795246 in pthread_mutex_lock () from /lib/libpthread.so.0
+ Trace 103080
Thread 5 (Thread -1219982448 (LWP 23541))
================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Aborted steveb@lithium:~$ Other information: This is f-spot 0.3.0 on Fedora Rawhide. Can't seem to reproduce, yet. Is this useful at all?
how many files were you importing?
Importing >8000 files.
This looks like a variation of the out of memory problems unless a specific photo is triggering it. Is is a generic thing or a specific photo?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!