(tracker-extract:5311): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed
Call to gst_discoverer_discover_uri(file:///home/roger/Documents/Old%20Stuff/Camtasia%20Studio/visualimpact.avi) failed: Unable to allocate memory
file:///home/roger/Documents/Old%20Stuff/Camtasia%20Studio/visualimpact.avi: No metadata or extractor modules found to handle this file
There is an interesting comment in the man page for tracker-extract.
"The actual extraction is done by a separate process. This is done to isolate the calling process from any memory leaks or crashes in the libraries Tracker uses to extract metadata."
Also happening in 17.04. Started happening after a fsck repair following a power failure. Could be related to lost/corrupt files.
Running tracker-extract manually on file shown in syslog gives the following.
roger@dragon: ~/Documents/ Old Stuff/Camtasia Studio$ tracker extract --verbosity= detailed visualimpact.avi ....... ....... ....... 2 ....... ....... ...... 1 tracker/ extract- rules) info_set_ format: assertion 'format != GST_VIDEO_ FORMAT_ UNKNOWN' failed info_to_ caps: assertion 'info-> finfo-> format != GST_VIDEO_ FORMAT_ UNKNOWN' failed
Tracker-Message: Starting tracker-extract 1.12.0
Tracker-Message: General options:
Tracker-Message: Verbosity .......
Tracker-Message: Sched Idle .......
Tracker-Message: Max bytes (per file) ................. 1048576
Setting priority nice level to 19
Loading extractor rules... (/usr/share/
Extractor rules loaded
MIME type guessed as 'video/x-msvideo' (from GIO)
gst_video_
gst_video_
(tracker- extract: 5311): GStreamer-CRITICAL **: gst_mini_ object_ unref: assertion 'mini_object != NULL' failed discover_ uri(file: ///home/ roger/Documents /Old%20Stuff/ Camtasia% 20Studio/ visualimpact. avi) failed: Unable to allocate memory /home/roger/ Documents/ Old%20Stuff/ Camtasia% 20Studio/ visualimpact. avi: No metadata or extractor modules found to handle this file
Call to gst_discoverer_
file://
There is an interesting comment in the man page for tracker-extract.
"The actual extraction is done by a separate process. This is done to isolate the calling process from any memory leaks or crashes in the libraries Tracker uses to extract metadata."