On 21/01/15 03:17, Julius Friedman wrote:
Sorry I was quite busy the past two days,but here is what I can gather by
my rough estimation as to why the library gets stuck...
The problem is easily reproducible from server to client and also effects
cases when the logic is used to handle messages inbound in server
implementations.
The loop initiated prior @ 1096 is executed `forever` and starts the
problem, if none of the required data is found within a few hundred reads
the context switching here becomes very bad and the CPU usage exhibited
made be look into this further and what was going on and how to replicate
it.
I have since been able to craft a message using my server implementation
which does replicate the behavior reliably through VLC and ffplay which I
outlined previously.
I have also outlined a few other issues I saw when testing some niche case
scenarios in my server such as long running requests which is how I can to
the stuff about polling for reading, none the less I will try to explain
the best I can but the issue is fairly obvious if you just feed the message
to VLC and step through the response also.
Could you please get me a test setup to check (or guide me how to get
your server deployed on a linux system)?
Just to make sure are you using the current Libav?
Thanks for the by-line report, tomorrow I'll be travelling and I hope to
read it while on the train.
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
