On Sat, 30 Dec 2017 13:22:37 -0800
Aaron Levinson wrote:
> On 12/30/2017 8:44 AM, wm4 wrote:
> > There is no POSIX error code for EOF - recv() signals EOF by simply
> > returning 0. But libavformat recently changed its conventionts and
>
> "conventionts" -> "conventions"
>
> > requires an exp
On 12/30/2017 8:44 AM, wm4 wrote:
There is no POSIX error code for EOF - recv() signals EOF by simply
returning 0. But libavformat recently changed its conventionts and
"conventionts" -> "conventions"
requires an explicit AVERROR_EOF, or it might get into an endless retry
loop, consuming 100%
Hi,
On Sat, Dec 30, 2017 at 11:44 AM, wm4 wrote:
> There is no POSIX error code for EOF - recv() signals EOF by simply
> returning 0. But libavformat recently changed its conventionts and
> requires an explicit AVERROR_EOF, or it might get into an endless retry
> loop, consuming 100% CPU while d
There is no POSIX error code for EOF - recv() signals EOF by simply
returning 0. But libavformat recently changed its conventionts and
requires an explicit AVERROR_EOF, or it might get into an endless retry
loop, consuming 100% CPU while doing nothing.
---
libavformat/tcp.c | 2 ++
1 file changed,
