Open arnaudleyder opened 8 years ago
Attached complete stream logs. flashhls.zip
net::ERR_CONTENT_LENGTH_MISMATCH means that there is a mismatch between signaled fragment length (in HTTP headers) and received fragment length. as u can see, it is considered as a parsing error.
Thanks for the reply. Thanks also for the amazing project and support. Is flashls supposed to recover from these kind of errors or is it expected that the player should stop functionning? As you can see in this case the player loadnextfragment() and then cancel demux in a loop just after the error shows in the log.
Thanks Arnaud
It is expected to recover. I didnt check the logs yet
Hi,
I have a live HLS stream: http://m-1.data.lt/m-1/smil:m-1.smil/playlist.m3u8 I am seeing an issue where our player based on OSMF/flashhls will stop playing video after about 15 minutes of playback and will enter infinite buffering. Below are the logs (latest Chrome 48 + Flash 20). I suspect it comes from:
Because after that it just keeps trying to load fragments DEBUG:loadnextfragment() with a DEBUG:TS: cancel demux.
I would like to understand what it means and what could cause this issue. I have other live streams running without issue so I am guessing it could be a transcoding or segmenting issue but I would like to narrow down the source of this issue so any help on interpretting those logs would be appreciated.