Opened 3 years ago

Closed 2 years ago

#5463 closed defect (needs_more_info)

random crashes when reading realtime updated metadata from text file

Reported by: m3gab0y Owned by:
Priority: important Component: undetermined
Version: git-master Keywords: crash
Cc: michael Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug: random crashes when reading realtime updated metadata from text file
How to reproduce:

ffmpeg -i 'http://149.13.0.81/nrj.ogg' -itsoffset 8.0 -i 'http://149.13.0.81/nrj.ogg' -loop 1 -i '/cnc/scr/radio.jpg' -filter_complex "scale=400:320,drawtext=fontfile=/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf: text='Radio Energy (Test)': fontcolor=white@0.8:fontsize=18: x=(w-text_w)/2:y=(h-text_h-line_h)/2+90,drawtext=fontfile=/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf: textfile='/cnc/scr/radio.txt': reload=1: fontcolor=white@0.8:fontsize=12: x=(w-text_w)/2:y=(h-text_h-line_h)/2+120" -r 25 -map 1:a -map 0:a -codec:v libx264 -profile:v high -preset veryfast -threads 0 -b:v 100k -maxrate 100k -bufsize 150k -g 400 -metadata publisher="m3gab0y" -metadata service_provider="root@m3gab0y.com" -metadata service_name="Radio (Test)" -c:a:1 libfdk_aac -b:a:1 16k -c:a:0 libfdk_aac -b:a:0 96k -f mpegts "udp://127.0.0.1@239.254.254.254:1000"

ffmpeg version 2.6.git Copyright (c) 2000-2015 the FFmpeg developers

built with gcc 4.9.2 (Debian 4.9.2-10)
configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
libavutil 54. 26.101 / 54. 26.101
libavcodec 56. 41.101 / 56. 41.101
libavformat 56. 34.100 / 56. 34.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100

Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Output logfile:
http://pastebin.com/FMpmECEW

It crashes at random but most crashes are when ffmpeg matches a write in the file (metadata upodate)
If this is not considered a bug, how can we resolve this? Maybe instruct ffmpeg to read the file at given intervals or receive this info from the outside via piped call, etc.?

Any info is welcome!

Change History (5)

comment:1 Changed 3 years ago by cehoyos

  • Component changed from ffmpeg to undetermined
  • Keywords crash added
  • Priority changed from normal to important

Please test current FFmpeg git head and prom vide backtrace, disassembly and register dump to make this a valid crash report.

comment:2 Changed 3 years ago by m3gab0y

Update with latest version as of yesterday from git, logfile:
http://www112.zippyshare.com/v/pUW49mrk/file.html

Same issue. Textfile is updated regularry with new metadata (artist + title playing on the particular radiostation)

You can reproduce this by running the same command and update the textfile regularry via for example php script.
OS is Ubuntu 14.04 LTS, ffmpeg compiled according to those instructions:
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu

Last edited 3 years ago by m3gab0y (previous) (diff)

comment:3 Changed 3 years ago by michael

http://www112.zippyshare.com/v/pUW49mrk/file.html
says "File has expired and does not exist anymore on this server"
also a minimal testcase would be helpful, the command line quoted in the first message is rater long and complex, are a the arguments needed for this to happen ?

comment:4 Changed 3 years ago by michael

  • Cc michael added

comment:5 Changed 2 years ago by cehoyos

  • Resolution set to needs_more_info
  • Status changed from new to closed

Please reopen if this is still reproducible and if you can provide console output, backtrace, disassembly and register dump, a testcase would also help.

Note: See TracTickets for help on using tickets.