#44 Segmentation Fault when doing a "full" scan

closed-invalid
nobody
None
5
2008-11-24
2008-11-23
Jan Rüegg
No

When doing a full scan on one of my directories via webinterface, I get a "segmentation fault" as below:

jan@MacBuntu:~$ mediatomb

MediaTomb UPnP Server version 0.11.0 - http://mediatomb.cc/

===============================================================================
Copyright 2005-2008 Gena Batsyan, Sergey Bostandzhyan, Leonhard Wimmer.
MediaTomb is free software, covered by the GNU General Public License version 2

2008-11-23 20:03:24 INFO: Loading configuration from: /home/jan/.mediatomb/config.xml
2008-11-23 20:03:24 INFO: Checking configuration...
2008-11-23 20:03:24 INFO: Setting filesystem import charset to UTF-8
2008-11-23 20:03:24 INFO: Setting metadata import charset to UTF-8
2008-11-23 20:03:24 INFO: Setting playlist charset to UTF-8
2008-11-23 20:03:24 INFO: Configuration check succeeded.
2008-11-23 20:03:24 WARNING: Sqlite3 database seems to be corrupt or doesn't exist yet.
2008-11-23 20:03:24 INFO: no sqlite3 backup is available or backup is corrupt. automatically creating database...
2008-11-23 20:03:24 INFO: database created successfully.
2008-11-23 20:03:24 INFO: Initialized port: 49153
2008-11-23 20:03:24 INFO: Server bound to: 192.168.1.11
2008-11-23 20:03:26 INFO: MediaTomb Web UI can be reached by following this link:
2008-11-23 20:03:26 INFO: http://192.168.1.11:49153/
2008-11-23 20:03:50 ERROR: iconv: Invalid or incomplete multibyte or wide character
2008-11-23 20:03:50 ERROR: iconv: Auf dem Highway ist wieder die H�lle los could not be converted to new encoding: invalid character sequence!
Segmentation fault

Doing a Basic scan works, but then some mkv - Videos won't get recognized as Videos and don't appear on the client.

I'm on a 64-bit Ubuntu 8.10 Intrepid, using Mediatomb from the sources.

For more information, just ask!

By the way: Great work! I love MediaTumb, especially the Transcode functionality ;-)

Discussion

  • Just found out that a basic scan does actually NOT work, and that this happens when mediatomb tries to access a file about 8.3 GB large...

     
  • Jin
    Jin
    2008-11-23

    In 99.9% of the cases this problem was caused by ffmpeg libraries (you'll find a number of posts with a similar problem).

    The fix is either to rebuild MediaTomb without ffmpeg support or to update your ffmpeg libs to a newer version.

    If you know what file causes the crash you may also try doing "ffmpeg -i thisfile" on the command line - just to confirm that ffmpeg crashes on it.

    Please close the PR once you confirm that it's the libav* libs that crash.

    Regarding mkv - possible that you may have to enter an extension to mimetype mapping for the mkv files and reimport them, check if file -i yourmovie.mkv returns something meaningful, if not add a custom mapping. And then of course, your device has to support the mkv container. But this is again a question for the forums...

     
  • Yup, ffmpeg crashes with a "ffmpeg -i". Sorry for the bug report, but I didn't find any of the other posts.

    File -i gives me a "application/octet-stream"... if it's not too much trouble, could you tell me how to do this custom mapping?

    I'll close the issue then. Thanks for the help!

     
  • Jan Rüegg
    Jan Rüegg
    2008-11-24

    (Wasn't logged in, the last comment is mine...)

     
  • Jan Rüegg
    Jan Rüegg
    2008-11-24

    • status: open --> closed-invalid