© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
So, there are a few things mentioned here, let me answer them:
1. Any case where you see SIGABRT is usually Tracker killing itself due to seriously high memory use. This has been removed for 1.3.x onwards. What this means is, instead of getting a SIGABRT and the process closing, your machine will be brought to its knees if there are broken 3rd party implementations OR files not following standards. This is usually the reason for SIGABRT, it's rarely a Tracker bug.
2. The tracker-extract process has recently had a fail-safe added to it, so if extraction attempts fail more than 'n' times, we will stop trying. This avoids the "login, fail, login, fail, etc" cycle.
3. If you're seeing high memory use, please file a bug upstream with the file(s) causing this and we will try to fix it. The same with slow down. Some people have crazy PDF content (for example) which can take a LOOONG time to extract and use GBs of memory. This is not Tracker's fault.
Finally, I want to add that the reason we have a tracker-extract process is EXACTLY because 3rd party content or libraries are not reliable enough and often deviate from standards. The process is built with crashing expected at some point, and we do try our best NOT to let this happen - but it's not always in our control.
Thanks,