GNOME Bugzilla – Bug 395310
Importing some photos makes F-Spot take 100% of CPU
Last modified: 2007-01-30 15:19:07 UTC
Please describe the problem: I've imported some pictures I'll attach to this bug. After that, F-Spot takes 100% of memory and never drops it. Even closing and reopening the program doesn't solve the problem. Those pics were taken with a Nokia 7250, and don't contain Exif infos. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 80010 [details] A picture which causes the problem.
The following is the console output of an import session of the picture. During the cpu load F-Spot doesn't output any error on the console. $ f-spot -p fspassa/ -b fspassa/ BaseDirectory is now fspassa/ PhotoDirectory is now /home/maxxer/fspassa/ Starting new FSpot server Reloading item changed item ImportCommand+SourceItem Scanning /home/maxxer/fspassa item changed open uri = file:///home/maxxer/fspassa/Immag044.jpg System.NullReferenceException: Object reference not set to an instance of an object at FSpot.JpegFile.get_Date () [0x00000] open uri = file:///home/maxxer/fspassa/Immag044.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/maxxer/fspassa/2007/1/11/Immag044.jpg open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg error checking orientation open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg cleanup context cleanup context open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg old = "" new = "" heading = "ASCII" value = f-spot version 0.3.0 len = 20 value = 2007:01:11 09:11:46 len = 19 value = 2007:01:11 09:11:46 len = 19 value = f-spot version 0.3.0 len = 20 value = 2007:01:11 09:11:46 len = 19 Saved 124 bytes item changed open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg error checking orientation open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg Stopping open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg error checking orientation open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg error checking orientation Reloading item changed open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg error checking orientation open uri = file:///home/maxxer/fspassa/2007/1/11/Immag044.jpg
hi maxxer, I'm not sure I understand your issue... the topic is about 100%CPU and the description about 100%memory... and you say that f-spot does not free its memory even after being killed ! btw, I can import your image just fine, getting the same logs as you, without any long term strange behavior with either cpu or memory
(In reply to comment #3) > hi maxxer, > > I'm not sure I understand your issue... the topic is about 100%CPU and the > description about 100%memory... > and you say that f-spot does not free its memory even after being killed ! Sorry the problem is about CPU usage. > btw, I can import your image just fine, getting the same logs as you, without > any long term strange behavior with either cpu or memory As I get that picture into F-Spot my cpu load goes 100%. I'm using F-Spot 0.3.0. I will try CVS today and will report back...
tested now, same identical behavior with latest SVN. What else can I do?
start f-spot, load your image kill f-spot if the cpu is still 100% used, use top (or ps or whatever) to check which process is running
(In reply to comment #6) > start f-spot, > load your image > kill f-spot > if the cpu is still 100% used, use top (or ps or whatever) to check which > process is running I'm already sure F-spot is taking the CPU, because I see it in top when f-spot is running, and when I close it the cpu returns to normal usage!
ah, when you kill f-spot, the cpu usage is 'normal' then ! sorry for the misunderstanding...
Created attachment 80022 [details] Screenshot A screenshot which shows cpu usage.
hi maxxer, this photo is corrupted, as reported by the gimp loader: "Corrupt JPEG data: 100 extraneous bytes before marker 0xd9" Probably yet another libexif bug. Which version of libexif are you using ??
(In reply to comment #10) > this photo is corrupted, as reported by the gimp loader: "Corrupt JPEG data: > 100 extraneous bytes before marker 0xd9" > > Probably yet another libexif bug. Which version of libexif are you using ?? 0.6.13
mmm, this version works here... if you strip the exif part, can you load it (so we're sure that the culprit is the exif part) ? you can strip exifs using jhead jhead -purejpg photo.jpg
I'm sorry, it seems that I cannot reproduce it anymore. So either it got fixed itself in the latest releases or I really don't know what happened :-) Thanks
Don't be sorry. ... closing it