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 739762 - Tracker crashes all the time
Tracker crashes all the time
Status: RESOLVED DUPLICATE of bug 737663
Product: tracker
Classification: Core
Component: Extractor
unspecified
Other Linux
: Normal normal
: ---
Assigned To: tracker-extractor
Depends on:
Blocks:
 
 
Reported: 2014-11-07 09:18 UTC by Vít Ondruch
Modified: 2015-01-13 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Comment 1 Vít Ondruch 2014-11-07 09:20:57 UTC
You can get more reports from Fedora's FAF server:

https://retrace.fedoraproject.org/faf/reports/420211/
Comment 2 Vít Ondruch 2014-11-07 09:26:41 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1133924
Comment 3 Vít Ondruch 2014-11-07 09:28:42 UTC
And this is list of all crashes caught by ABRT in Fedora, may be you can fix all of them in once.

https://retrace.fedoraproject.org/faf/problems/hot/*/*/tracker/
Comment 4 Vít Ondruch 2014-11-07 09:30:15 UTC
This might give you idea what was wrong recently:

https://retrace.fedoraproject.org/faf/reports/list/*/tracker/new/
Comment 5 Martyn Russell 2014-11-10 10:00:01 UTC
Hi Vit, the bugs you've reported are all quite different.

1. https://bugzilla.redhat.com/show_bug.cgi?id=1157177
This looks like a GStreamer bug, not a Tracker bug.

2. https://bugzilla.redhat.com/show_bug.cgi?id=1157176
This has been fixed in master - well, I say fixed, you won't get SIGABRT any more, your machine will just die when rogue files or libraries bring your machine to your knees. This SIGABRT is a precaution to STOP that happening, but we're getting a lot of bug reports blaming Tracker instead.

3. https://bugzilla.redhat.com/show_bug.cgi?id=1119251
This has been fixed in 1.0.2, 1.2.0 and I could add it into a 0.16.6 if people see it there.

There majority of crashers you're seeing are related to tracker-extract and SIGABRT, Tracker is using setrlimit() which signals SIGABRT when massive memory or CPU is used due to 3rd party libraries (Like GStreamer or libgsf, etc) or if you have dodgy content (entirely possibly with MP3s written outside the standards - for example).

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 6 Vít Ondruch 2014-11-10 11:51:26 UTC
Hi Martyn,

Thanks for looking into this and for explanation. Would you mind to take a look at:

https://bugzilla.redhat.com/show_bug.cgi?id=1133924

This seems to be the latest from the series.
Comment 7 Martyn Russell 2014-12-02 10:47:54 UTC
(In reply to comment #6)
> Hi Martyn,
> 
> Thanks for looking into this and for explanation. Would you mind to take a look
> at:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1133924
> 
> This seems to be the latest from the series.

This is no longer relevant, the code causing this has been removed.
Comment 8 Vít Ondruch 2014-12-03 17:18:11 UTC
Thenks. After last updates of my Rawhide, I don't observe tracker crashes anymore. This is great! Thanks Martyn.
Comment 9 Martyn Russell 2014-12-04 12:58:26 UTC
(In reply to comment #8)
> Thenks. After last updates of my Rawhide, I don't observe tracker crashes
> anymore. This is great! Thanks Martyn.

You're welcome! :)
Comment 10 Martyn Russell 2015-01-13 15:06:28 UTC

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