After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630860 - f-spot huge memory and CPU usage while trying to import folder full of CR2 images
f-spot huge memory and CPU usage while trying to import folder full of CR2 im...
Status: RESOLVED DUPLICATE of bug 633972
Product: f-spot
Classification: Other
Component: Import
0.8.0
Other Linux
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-28 22:33 UTC by Nuno Ferreira
Modified: 2010-12-15 01:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nuno Ferreira 2010-09-28 22:33:58 UTC 
On the import dialog I choose a folder that has (on its children folders) around 400 cr2 photos. It works for some seconds and it settles, showing the thumbnails for the first photos.

If I then try scroll down the preview pane f-spot's memory usage skyrockets to ~2.8GB and it just hangs there using 100% CPU.
Comment 1 Nuno Ferreira 2010-09-28 23:03:30 UTC 
Some additional comments, also tried with a smaller folder and can also reproduce the problem.

Also running with --debug yields nothing, below are the last output lines, that are printed before scrolling down.

[1 Debug 23:56:01.951] Received controller event: SourceChanged
[1 Debug 23:56:01.974] Received controller event: PhotoScanStarted
[1 Debug 23:56:03.897] open uri = file:///mnt/nfs/media/photos/2010/01/01/IMG_8598.CR2
[1 Debug 23:56:04.147] Received controller event: PhotoScanFinished
[1 Debug 23:56:09.068] Loading image took 6.979141
Comment 2 Nuno Ferreira 2010-10-01 11:25:53 UTC 
I think the problem is with Taglib, using the example ParsePhoto from Taglib with several (~40) cr2 as parameter displays the same symptoms
Comment 3 Pat Suwalski 2010-12-14 18:31:50 UTC 
I think this might be addressed by the patch in bug #633972.
Comment 4 Nuno Ferreira 2010-12-15 01:49:11 UTC 
(In reply to comment #3)
> I think this might be addressed by the patch in bug #633972.

I just tested it, with that patch I was able to import ~2000 CR2 photos with no significant increase in memory usage, so it appears the patch works and this is the same bug.

*** This bug has been marked as a duplicate of bug 633972 ***