Memory leak when creating segment references from a timeline
See original GitHub issueHave you read the FAQ and checked for duplicate open issues? Yes
What version of Shaka Player are you using? v3.0.6-master
Can you reproduce the issue with our latest release version? Yes
Can you reproduce the issue with the latest code from master
?
Yes
Are you using the demo app or your own custom app? Both
If custom app, can you reproduce the issue using our demo app? Yes
What browser and OS are you using? Chrome Version 87.0.4280.88 (Official Build) (x86_64) MacOS 11.0.1
For embedded devices (smart TVs, etc.), what model and firmware version are you using? Chromecast (2nd generation)
What are the manifest and license server URIs?
What did you do? Playing our Dash live stream that contains 90 minutes of buffer.
What did you expect to happen? No buffering like v2.5.x version.
What actually happened? We found the issue within our app with the latest Chromecast CAF receiver update (November 22, 2020) that use Shaka 3.0.x. With our live stream containing 90 minutes of buffer, we notice high level of buffering issue with our customer.
With some investigation, I found that Shaka player leak memory with Dash live manifest.
Into my Chromecast receiver app, I logged the usedJSHeapSize
and the heap size never stop growing.
09:49:15.562 Shaka test /// usedJSHeapSize: 97.607819 MB /// lower usedJSHeapSize: 27.552935 /// higher usedJSHeapSize: 98.064532
09:49:15.564 Shaka test /// usedJSHeapSize increased 70 MB in 344 seconds since beginning of live playback session
It seems that we are not alone with this issue - https://issuetracker.google.com/issues/173897425
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (6 by maintainers)
Top GitHub Comments
Yes. I was doing test passes yesterday, and had some issues crop up with the v2.5 cherry-picks that I still need to resolve.
It has been cherry-picked for v3.0.7. We’re short-handed right now, on top of which we have holidays at the moment. I will plan to release v3.0.7 in the week of January 5 at the latest.