tracker-extract crashed with SIGSEGV in gst_iterator_next()

Bug #339445 reported by Derrick Neve
6
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: tracker

I don't even know what "tracker" is! I had just turned my laptop on and was preparing to read a flash SD disk when I got the message that there was a crash so I did as suggested and filed the problem report.

Good luck!

By the way, I am using 9.04 (updated last night from 8.10) but my screen is unusable so I'm going back to 8.10. I just booted up to backup all my files. Also I find I have no flash player on the web. Anyway, I'll wait for the general release.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/tracker/tracker-extract
NonfreeKernelModules: fglrx
Package: tracker 0.6.90-1ubuntu2
ProcCmdline: /usr/lib/tracker/tracker-extract
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: tracker
StacktraceTop:
 gst_iterator_next () from /usr/lib/libgstreamer-0.10.so.0
 gst_iterator_next () from /usr/lib/libgstreamer-0.10.so.0
 gst_iterator_fold () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: tracker-extract crashed with SIGSEGV in gst_iterator_next()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Derrick Neve (djn-microtec) wrote :
Revision history for this message
Martyn Russell (martyn-lanedo) wrote :

Hi,

Can you find out which file caused this crash? We are constantly fixing the extractors and this might have already been fixed. It looks like it was a media file of some sorts since GStreamer is in the back trace. Any chance you could send us the file so we can test with it? It may already be fixed in TRUNK.

Better yet, if you could test with TRUNK, that would be really helpful. We are planning a release this week. It would be great to fix this if it is still an issue.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gst_iterator_next (it=0x80808080, elem=0xbfa64f88) at gstiterator.c:283
gst_iterator_next (it=0x9b1a2b8, elem=0xbfa64f88)
gst_iterator_fold (it=0x9b1a2b8,
iterator_activate_fold_with_resync (iter=0x9b1a2b8,
gst_element_pads_activate (element=0x9baf280, active=0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in tracker:
importance: Undecided → Medium
Revision history for this message
Martyn Russell (martyn-lanedo) wrote :

Thanks for the additional information here. Looking at the code, it all seems fine. Unless this is some internal GStreamer bug, I don't see what is going wrong here.

Are you able to send us the file which causes this situation? You can probably test it in a stand alone manner using tracker-extract (the --help should provide you with information on how to use it).

Thanks

Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in tracker (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.