Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shaka Player Webos loss of performance to a standstill #3890

Closed
pedrosilvabos opened this issue Jan 20, 2022 · 2 comments
Closed

Shaka Player Webos loss of performance to a standstill #3890

pedrosilvabos opened this issue Jan 20, 2022 · 2 comments
Labels
status: archived Archived and locked; will not be updated type: question A question from the community

Comments

@pedrosilvabos
Copy link

Have you read the Tutorials?
YES

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

What version of Shaka Player are you using?
3.0.10

I have shaka working for Tizen and webos environents, with the same code.

The test team has a stress test that will open a stream let it play for 10 minutes, turn it off for 3 minutes and then play it again for another 10 minutes, this for at lest 50 cycles.

It is good to understand that when the turn off the stream, shaka player is infact destroyed and they go to a Full Info Page inside the app.

Tizen has no problem, and could play and stop all day.
Webos (all versions) after around 29 cycles will start to downgrade the bitrate (and will not pickup after) and increase the buffering, and around 10 cycles later it will simply not play, and produce eternal buffering.

This is does not happen on chrome either.

Using monitoring tools for webos and checking memory and network usage, there really isn't anything happening, all values look good both memory and cpu.

I read that shaka does not keep buffering.
Does anyone have any idea what could be causing this?
I can provide the manifest, but since it is attached to a DRM please let me know ahead so I can provide fresh links.

Thank you in adavance!

@pedrosilvabos pedrosilvabos added the type: question A question from the community label Jan 20, 2022
@avelad
Copy link
Collaborator

avelad commented May 3, 2022

Hi @pedrosilvabos. In version 4.0 we have resolved #4062 Can you try again with this version? Thanks!

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 3, 2022
@github-actions
Copy link
Contributor

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.

@github-actions github-actions bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 10, 2022
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 9, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated type: question A question from the community
Projects
None yet
Development

No branches or pull requests

2 participants