Curtis Lacy <[email protected]> added the comment:
I think I'm seeing an issue rooted in this as well. I'm using ffmpeg as a
library through JNI from a Java application, and the call to av_open_input_file
is not only blocking indefinitely if it never receives data, I also can't
interrupt that thread, so I can't cancel the request.
Sometimes Thread.interrupt() works just like it's supposed to (if the url I'm
connecting to is "udp://{whatever}"). If my URL is "rtp://{whatever}",
Thread.interrupt() doesn't appear to be honored by the native thread.
Thread.kill() doesn't even seem to do it (and is generally frowned on anyhow).
________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/issue539>
________________________________________________
