[FFmpeg-trac] #1980(undetermined:new): ffmpeg process hangs with 100% CPU when getting a live rtsp stream (on redhat linux)
FFmpeg
trac at avcodec.org
Tue Dec 4 09:28:48 CET 2012
#1980: ffmpeg process hangs with 100% CPU when getting a live rtsp stream (on
redhat linux)
--------------------------------+----------------------------------------
Reporter: muthuk | Owner:
Type: defect | Status: new
Priority: normal | Component: undetermined
Version: 1.0 | Resolution:
Keywords: rtsp | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------+----------------------------------------
Comment (by cehoyos):
Replying to [comment:4 muthuk]:
> Replying to [comment:3 cehoyos]:
> > Since no developer is able to reproduce the problem (because of your
rtsp address), a backtrace is necessary.
> > Please run "$ gdb ffmpeg_g", then "r -i rtsp... " and when ffmpeg
hangs, you interrupt it with Ctrl-C and type "bt" to get a backtrace,
please post it here.
>
> I actually run/launch these from a perl script (launches 25 instances
every ~6 minutes) and they fail at random (after 15-20 minutes or so). I
don't think launching each invocation in gdb is feasible. I realize
however that i can attach to an ffmpeg process & take a backtrace (cmd-
line attach).
I have never done it myself but this sounds like a good idea.
> Also please let me know how to build ffmpeg with debug enabled.
$ ./configure && make ;-)
Your configure line produces two executables, ffmpeg_g contains debug
symbols, I suspect --disable-stripping leaves the symbols also in ffmpeg.
(I only realize now you are using --disable-yasm. This is actually a good
idea for debugging, but don't forget to remove it in the future, it hurts
performance.)
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1980#comment:5>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list