crashes in tracker-extract should be ignored
** Changed in: tracker (Ubuntu)
Status: New => Invalid
--
Tracker crashes ocasionally :S
https://bugs.launchpad.net/bugs/182037
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
(1) The self-destruction should happen with a signal that does not
indicate a non-deliberate crash (i. e. one that does not cause the
kernel to dump core). SIGTERM or SIGKILL are quite appropriate and don't
cause apport reports.
(2) If you really need a 'crashy' signal like SIGSEGV and want to ign
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: tracker (Ubuntu)
Importance: Undecided => Medium
Status: New => Incompl
I forgot this part of the log :)
22:57 < pochu> jamiemcc: could you point me to the code where
tracker-extract is called with that time limit? I'll ask pitti/file a bug
against apport to ignore such cases.
22:58 < jamiemcc> look for setrlimit call (its calle din several places)
22:58 <
This was the discussion we had on IRC:
20:28 < pochu> hey jamiemcc. There are some reports about tracker-extract
crashing. Since you said trackerd kills tracker-extract if it's taking a long
time, I'm wondering whether it would be possible to check if the file is too
long first and if it is
This is a crash in tracker-extract when extracting metadata from a big
video. I guess all the crashes are in tracker-extract when indexing
/media/sda3/Videos/
FYI, tracker-extract won't crash, but terminates if it takes more than
10(?) seconds to extract the metadata of a file, or if the RAM used
