shaka-player: Memory leak on multi-period streams

Have you read the FAQ and checked for duplicate open issues? Yes

If the problem is related to FairPlay, have you read the tutorial?

Yes

What version of Shaka Player are you using?

4.2.x => 4.7.x

Can you reproduce the issue with our latest release version? Yes

Can you reproduce the issue with the latest code from main? Yes

Are you using the demo app or your own custom app? Demo app

If custom app, can you reproduce the issue using our demo app? Yes

What browser and OS are you using? chrome, windows

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

https://d24rwxnt7vw9qb.cloudfront.net/v1/dash/e6d234965645b411ad572802b6c9d5a10799c9c1/All_Reference_Streams/4577dca5f8a44756875ab5cc913cd1f1/index.mpd

What configuration are you using? What is the output of player.getConfiguration()?

Default

What did you do?

Play stream and take memory heap snapshots using chrome dev tools at different times

What did you expect to happen? Memory heap to be stable

What actually happened?

Memory heap grows consistently for multi-period streams. On mono-period streams, we dot not notice the same result.

Please find screenshots:

  • Heap snapshots to illustrate inscrease of memory consumption: image

  • Snapshots comparison after 45 minutes image

  • Details and allocation call stack (based on v4.5.x) of retained objects image

Please note that all objects (Text, Element, NodeList …) are allocated in the same place.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (12 by maintainers)

Commits related to this issue

Most upvoted comments

thanks for the update @bbert! Since we have already improved everything we could, I proceed to close the issue as resolved!

we should reopen this.