Tizen: DASH live streams are freezing after 15 - 20 minutes of playback #1195
Comments
|
Hi @TomaszKowalik, It weirdly looks like there's it does not succeed to buffer segments, because new video segments are loaded and pushed, but are then not found in the buffer. By looking in your logs at what is present in the buffer, I see that it seems to not be properly garbage collecting old segments (~80 seconds of ~3Mbps video behind the current position seems high to me) :/ Can you test by calling
|
|
Hi @peaBerberian , thank you for your answer |
|
Ah, perhaps! Perhaps the issue is somewhat linked to garbage collection pressure, iself due to frequent heavy manifest updates ? Can you try playing with a Doc for For example, you can try: player.loadVideo({
// ...
transportOptions: {
minimumManifestUpdateInterval: 10000,
},
startAt: {
fromLastPosition: -20,
},
});Thanks |
|
So I've tried with and without |
|
:/ |
|
Indeed, with this setting, stream was playing nicely and after around 30 minutes it started to throw a lot of This is what I found in the logs before the error: This log looks quite unusual: Looks like it led to ratechange event What could we do to enchance this buffer handling, also for higher quality? |
Ah yes, this is Tizen! Tizen devices are particularly hard to handle because they sometimes have their own behaviors in conflict with the RxPlayer. If updating the played bitrate changes the delay at which the issue is encountered, it has high chances of being linked to memory usage. Can you now re call at least the |
|
After using But I've noticed another strange thing today: stream is crashing after ~15 minutes, but if I'll play the stream for about 8 minutes, then stop it with eg back button, and then start the stream again -> it will crash after ~7 minutes then. So looks like that no matter if stream is playing continuously or not, it will crash after this particular period of playback time... |
|
For the In that situation you should seek back at a position superior to As for the more important bitrate-related error, it's strange that it triggers after 15 minutes of playback, regardless of if we're ourselves cleaning the buffer regularly and even more strange that it is still happening if we quit and restart the content in between. Does Tizen provide some tools to monitor memory usage and CPU usage to see if there's a correlation? |
|
I handled this Samsung offers some tools for memory usage monitoring, but not for Smart TV "for safety reasons" :/ The only thing I can do is to make calls to Tizen's API for total and available memory and for CPU load, and print it in the logs. After doing so, indeed available memory was dropping down. After starting the stream: After 10 minutes: Before the crash: And after closing the stream, available memory stays at the same level. As for Representation I can see few in the manifest: When I played the stream with the locked bitrate to use the parameters from the representation with bandwidth="2337000", then after 30 minutes of streaming available memory was around With the lowest quality it looks like that available memory is also dropping down, but very slowly, so crash probably would also happen after longer period of time. Additional manifest settings: But Today I played
This crashes seem rather to be related to stream quality. I checked the livestreams from provider where I didnt noticed the crash before, and their quality were eg On the Samsung 2020 however, when playing same streams, with same paramaters in the manifests I was also seeing memory drops to eg: But streams were playing fine and I saw it was freeing the memory as its value was also raising. We prepared the app that can be run on a PC, I'll send you link and credentials via email |
|
Hi and thanks! Ok, so the crash does seem to happen when there's around ~145MB of memory left and memory doesn't seem to be collected once stopped... There's many questions left here but it's a very good start. |
|
@peaBerberian |
We found an issue that occurs on some Tizen models when using rxPlayer 3.29.0. I was able to reproduce it on Tizen 2018, 2019 but not on Tizen 2020 and 2021. DASH live streams from one of our providers are affected.
After starting the stream it's playing fine for about 15 - 20 minutes, then it freezes, and leads to session being aborted.
We are starting the stream with these parameters:
I've collected some logs during debugging session with
RxPlayer.LogLevelset to"DEBUG"Just before the freeze I think its the first unusual message from the player:
and it leads to:
Then these logs seem to be repeating like that with
MEDIA_TIME_BEFORE_MANIFESTerrors, and ultimately it leads to session being aborted.I was also looking in the network tab of the devTools, and the unusual thing that I can see is that when the freeze occured, this
init.m4vrequest was made:What might be the possible cause of such behavior? Please let me know if there is any other information I could provide.
The text was updated successfully, but these errors were encountered: