I just managed to reproduce this error using the test image. Had to drop down swiftly into a virtual tty to kill f-spot before it ate every last byte of memory and swap. I don't get the same issue with any other jpeg images in f-spot.
John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
