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 599472 - f-spot take all CPU and memory and crash when importing a large number of photos
f-spot take all CPU and memory and crash when importing a large number of photos
Status: RESOLVED OBSOLETE
Product: f-spot
Classification: Other
Component: Import
0.6.x
Other Linux
: Normal major
: 0.7.2
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-24 08:56 UTC by Sylvain ZUCCA
Modified: 2010-08-02 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sylvain ZUCCA 2009-10-24 08:56:28 UTC 
Version f-spot 0.6.1.3 on Ubuntu karmic 9.10
Laptop Toshiba with 1Gb of memory

All my photos (~10000) are stored on usb drive on diverse directories under the repertory "images"

I wants f-spot to become the personal photo management for the collection

I tell f-spot to import all from the main repertory "images"

After a while, i see the cpu and the memory growing until reach the maximum and f-spot crashes after importing ~2500 photos

Why the memory is not correctly managed in this case ?

For comparison, picasa import all in 1 time without any problem
Comment 1 Stephane Delcroix 2009-10-26 09:26:52 UTC 
We might have a bug there, but that's an unusual test case (i.e. once your collection is in, you're safe).

I'd say import in smaller chunks for now. I'll keep that in mind while reworking the import process.
Comment 2 Ivo Smelhaus 2010-05-25 21:40:08 UTC 
I suffer with this problem as well. I tried to use F-spot and the first step was importing photos (~ 30 000) but I was never succeeded. After some few thousand pictures I run out of memory (2G + 2G swap). My CPU is quite stable (~50% of Athlon 6400). For me it makes F-spot unusable unless otherwise I like it.
Comment 3 Ruben Vermeersch 2010-06-14 21:02:45 UTC 
With current F-Spot from git (or the 0.7.0 release which will be out in 2 days), this should not be that much of an issue anymore, memory usage during import stays much more constant. Could you retest this?
Comment 4 Tobias Mueller 2010-07-31 11:54:06 UTC 
Closing as OBSOLETE as per last comment. Please reopen if this issue still exists.