GNOME Bugzilla – Bug 537230
f-spot hangs after a few minutes of use
Last modified: 2008-06-09 08:18:01 UTC
Steps to reproduce: 1. use f-spot 2. go into the editor 3. don't edit any files, just delete them from the drive 4. f-spot hangs Stack trace: :; f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** Initializing Mono.Addins Starting new FSpot server Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time Reloading Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time item changed open uri = file:///[...]/1028-215357.jpg error checking orientation open uri = file:///[...]/1028-215357.jpg open uri = file:///[...]/1029-133002.jpg open uri = file:///[...]/1029-133002.jpg error checking orientation (f-spot:24606): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. open uri = file:///[...]/1029-140949.jpg open uri = file:///[...]/1029-140949.jpg error checking orientation open uri = file:///[...]/1029-140907.jpg open uri = file:///[...]/1029-140907.jpg error checking orientation open uri = file:///[...]/1029-132852.jpg open uri = file:///[...]/1029-132852.jpg error checking orientation open uri = file:///[...]/1029-132647.jpg open uri = file:///[...]/1029-132647.jpg error checking orientation open uri = file:///[...]/1029-131036.jpg open uri = file:///[...]/1029-131036.jpg error checking orientation Other information: F-spot is not reponding to anything so I ran strace on it. :; strace -p 24606 Process 24606 attached - interrupt to quit restart_syscall(<... resuming interrupted call ...>^C <unfinished ...> Process 24606 detached :; strace -fp 24606 Process 24613 attached with 6 threads - interrupt to quit [pid 24607] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 24606] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 24608] futex(0xf76941e0, 0x80 /* FUTEX_??? */, 27 <unfinished ...> [pid 24609] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 24612] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 24613] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 24612] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 24612] gettimeofday({1212922281, 524093}, NULL) = 0 [pid 24612] futex(0xf769501c, 0x81 /* FUTEX_??? */, 1) = 0 [pid 24612] clock_gettime(CLOCK_REALTIME, {1212922281, 524154656}) = 0 [pid 24612] futex(0xf7695038, 0x80 /* FUTEX_??? */, 5303 <unfinished ...> [pid 24613] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 24613] gettimeofday({1212922281, 526044}, NULL) = 0 [pid 24613] futex(0xf7695088, 0x81 /* FUTEX_??? */, 1) = 0 [pid 24613] clock_gettime(CLOCK_REALTIME, {1212922281, 526106551}) = 0 [pid 24613] futex(0xf76950a4, 0x80 /* FUTEX_??? */, 5303 <unfinished ...> [pid 24609] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 24609] gettimeofday({1212922281, 557988}, NULL) = 0 [pid 24609] futex(0xf7694668, 0x81 /* FUTEX_??? */, 1) = 0 [pid 24609] clock_gettime(CLOCK_REALTIME, {1212922281, 558034414}) = 0 [pid 24609] futex(0xf7694684, 0x80 /* FUTEX_??? */, 5391 <unfinished ...> [pid 24612] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
I have a Core 2 machine running 2.6.25-2-amd64 from Debian unstable but my userland is still 32 bit. F-spot 0.4.2 doesn't appear to hang as quickly.
my original bug report concerned 0.4.3.1-1 (Debian unstable) with the scrolling thumbs nails in the editor window turned on.
F-spot 0.4.2-1 hangs as well with a "Xlib: unexpected async reply (sequence 0x104d78)!" error message. :; strace -fp 25502 Process 25512 attached with 6 threads - interrupt to quit [pid 25502] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 25503] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 25504] futex(0xf764c1e0, 0x80 /* FUTEX_??? */, 1421 <unfinished ...> [pid 25508] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 25511] restart_syscall(<... resuming interrupted call ...> <unfinished ...> [pid 25512] restart_syscall(<... resuming interrupted call ...>) = -1 ETIMEDOUT (Connection timed out) [pid 25512] gettimeofday({1212955896, 591100}, NULL) = 0 [pid 25512] futex(0xf7651984, 0x81 /* FUTEX_??? */, 1) = 0 [pid 25512] clock_gettime(CLOCK_REALTIME, {1212955896, 591175668}) = 0 [pid 25512] futex(0xf76519a0, 0x80 /* FUTEX_??? */, 3663 <unfinished ...> [pid 25511] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 25508] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 25511] gettimeofday( <unfinished ...> [pid 25508] gettimeofday( <unfinished ...> [pid 25511] <... gettimeofday resumed> {1212955896, 605083}, NULL) = 0 [pid 25508] <... gettimeofday resumed> {1212955896, 605118}, NULL) = 0 [pid 25511] futex(0xf764d88c, 0x81 /* FUTEX_??? */, 1 <unfinished ...> [pid 25508] futex(0xf764c95c, 0x81 /* FUTEX_??? */, 1 <unfinished ...> [pid 25511] <... futex resumed> ) = 0 [pid 25508] <... futex resumed> ) = 0 [pid 25511] clock_gettime(CLOCK_REALTIME, <unfinished ...> [pid 25508] clock_gettime(CLOCK_REALTIME, <unfinished ...> [pid 25511] <... clock_gettime resumed> {1212955896, 605198284}) = 0 [pid 25508] <... clock_gettime resumed> {1212955896, 605229320}) = 0 [pid 25511] futex(0xf764d8a8, 0x80 /* FUTEX_??? */, 667019 <unfinished ...> [pid 25508] futex(0xf764c978, 0x80 /* FUTEX_??? */, 670877 <unfinished ...> [pid 25512] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
*** This bug has been marked as a duplicate of 333071 ***