GNOME Bugzilla – Bug 660965
100% CPU-load / segfault processing png-file
Last modified: 2013-02-26 11:14:23 UTC
Created attachment 198310 [details] 2 pictures, "Crystal.png" and "SomethingCross.png" while tracker made its initial index, tracker-extract used 100% of my cpu. I found out, that it was processing on the attached "Crystal.png" (part of the manslide 3d-slideshow-editor [1]). After killing the process it was immediately hanging on the next picture, "SomethingCross.png", until I killed it again. /usr/libexec/tracker-extract -f ….png ends with an segmentation fault. I am using tracker 0.12.3-r2 from the gnome-overlay for gentoo with USE="elibc_glibc exif firefox-bookmarks flac flickr gif gnome-keyring gstreamer gtk jpeg laptop mp3 nautilus networkmanager pdf playlist rss tiff vorbis xml -applet -doc -eds -gsf -iptc -test -thunderbird -upnp -xine -xmp" [1] manslide: http://qt-apps.org/content/show.php/Manslide?content=55945
On my machine, running "/usr/libexec/tracker-extract -f Crystal.png" results in a segmentation fault. Here is the backtrace:
+ Trace 228687
Incidentally, this is with libpng-1.5.5.
(In reply to comment #0) > Created an attachment (id=198310) [details] > 2 pictures, "Crystal.png" and "SomethingCross.png" > > while tracker made its initial index, tracker-extract used 100% of my cpu. I > found out, that it was processing on the attached "Crystal.png" (part of the > manslide 3d-slideshow-editor [1]). After killing the process it was immediately > hanging on the next picture, "SomethingCross.png", until I killed it again. > > /usr/libexec/tracker-extract -f ….png ends with an segmentation fault. > > I am using tracker 0.12.3-r2 from the gnome-overlay for gentoo with > USE="elibc_glibc exif firefox-bookmarks flac flickr gif gnome-keyring gstreamer > gtk jpeg laptop mp3 nautilus networkmanager pdf playlist rss tiff vorbis xml > -applet -doc -eds -gsf -iptc -test -thunderbird -upnp -xine -xmp" > > > [1] manslide: http://qt-apps.org/content/show.php/Manslide?content=55945 Hello Matthias, interesting you have 100% CPU. Is tracker configured to index only when idle on your machine? (in tracker-preferences) Also, if you run the command yourself on the command line: /usr/libexec/tracker-extract -f $file Does it do the same thing? (In reply to comment #1) > On my machine, running "/usr/libexec/tracker-extract -f Crystal.png" results in > a segmentation fault. Here is the backtrace: I don't get that here, but I am still using Natty. I am using 1.2.44-1ubuntu3.1. I will try on Oneiric beta tomorrow (which should have a newer version of libpng) to see if anything changes here.
(In reply to comment #2) > Hello Matthias, interesting you have 100% CPU. Is tracker configured to index > only when idle on your machine? (in tracker-preferences) I changed the configuration a few times so I can't remember which setting it was when it was hanging > Also, if you run the command yourself on the command line: > > /usr/libexec/tracker-extract -f $file segfault its also a segfault with the version 0.12.4 of tracker installed today btw: I have installed libpng in Versions 1.2.46 and 1.4.8-r1. I don't know, which version tracker-extract is using. They were both installed before tracker.
same for 0.12.5
*** Bug 672678 has been marked as a duplicate of this bug. ***
*** Bug 675933 has been marked as a duplicate of this bug. ***
Both bug 672678 and bug 675933 have good stack traces it's worth noting... For now upgrading this bug report!
Created attachment 237407 [details] [review] Avoid a double-free in the png extractor The software member of the exif data was getting freed twice. So whenever you deal with a png that has this field set to a non-NULL value, you get a segfault.
Review of attachment 237407 [details] [review]: Looks good.
Attachment 237407 [details] pushed as 4306640 - Avoid a double-free in the png extractor
cherry picked to the tracker-0.14 branch as well
Thanks Matthias, I will do a last (hopefully) release of 0.14.6 in the coming weeks and then start the 0.16.0 releases just as GNOME 3.8 comes out.