The first stack trace is unfortunately useless. The second one seems to be a bug in GStreamer. That's probably Jim Hodapp's domain.
Mediascanner has protection against files that cause GStreamer to crash the process from under it. It remembers broken files and skips them when it is restarted. Thus Mediascanner should never get stuck in a crash loop. The unfortunate state of media files and gstreamer is that we can probably never get rid of these crashes totally. Therefore unless someone can demonstrate a crash loop in Mediascanner (rather than just one crash per broken file) this bug should probably be downgraded from critical. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1364466 Title: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner- service-2.0': double free or corruption (fasttop): ADDR *** Status in “mediascanner2” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.104+14.10.20140825-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1364466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
