Opened 8 years ago
Last modified 8 years ago
#6372 new defect
Live Streaming - process no longer terminates
Reported by: | ethernetweb | Owned by: | |
---|---|---|---|
Priority: | important | Component: | ffmpeg |
Version: | 3.2.4 | Keywords: | rtmp |
Cc: | cheeto_crunch@yahoo.com | Blocked By: | |
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
Recently installed ffmpeg on a new server (which provided me with a newer version).
Old Version:
ffmpeg version 3.0.2-4~bpo8+1 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 4.9.2 (Debian 4.9.2-10)
On the old version, the ffmpeg process would stop running if the RTMP stream ceased to publish. Event handlers in our automated software would detect this "end" and proceed to handle it as the code designates.
In the new version, the ffmpeg continues to process and run indefinitely when the input ceases to exist. There also appears to be no way to suggest that the process SHOULD stop if the input ceases to exist. We have spent hours looking for a work-around but nothing is effective in stopping the process when an rtmp input ceases to publish.
How to reproduce:
% /usr/bin/ffmpeg -hide_banner -nostdin -y -threads 2 -i rtmp://localhost/live-test/test -acodec aac -vcodec copy -f flv rtmp://localhost/live-push/test ffmpeg version 3.2.4-1~bpo8+1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 4.9.2 (Debian 4.9.2-10)
Change History (4)
comment:1 by , 8 years ago
Cc: | added |
---|---|
Component: | undetermined → ffmpeg |
Version: | unspecified → 3.2.4 |
follow-up: 3 comment:2 by , 8 years ago
comment:3 by , 8 years ago
Replying to stevenliu:
try to use -timeout to control the exit step when connecion timeout.
Thank you for your response.
I've tried that already. All it does is change the rtmp:// protocol to tcp:// and it fails to function.
comment:4 by , 8 years ago
Please test current FFmpeg git head and provide the command line you tested together with the complete, uncut console output to make this a valid ticket.
try to use -timeout to control the exit step when connecion timeout.