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

[BUG] - Stresstest fails to load video after time #344

Open
aussiedwarf opened this issue Dec 2, 2024 · 1 comment
Open

[BUG] - Stresstest fails to load video after time #344

aussiedwarf opened this issue Dec 2, 2024 · 1 comment
Assignees
Labels
bug Something isn't working never-stale

Comments

@aussiedwarf
Copy link

UE Version:
Observed in UE 5.5.1 but probably present in all versions.

Frontend Version:
Observed in UE5.5 but probably present in all versions with stresstest.

Problem component
Frontend

Description
The Infra Stresstest will stop loading video after 10-30 minutes. It will report, waiting for video. Examining webrtc-internals, it says video is being received and decoded fine. The console will report [Intervention] Blocked attempt to create a WebMediaPlayer as there are too many WebMediaPlayers already in existence. See crbug.com/1144736#c27.

Steps to Reproduce:

  1. Start the signaling server
  2. Start UE and connect Pixelstreaming to the SS
  3. Start the stresstest
  4. after 10-30 minutes, video will no longer load and each media element will say "WebRTC connected, waiting for video", and console error "[Intervention] Blocked attempt..."

Expected behavior

  1. The stresstest should continue to load and display video.

Platform (please complete the following information):

  • OS: Windows 10
  • Chrome 131.0.6778.86

Additional context
According to this Chrome may only support up to 1,000 media elements. But setting the following before their destruction supposedly fixes the problem.

mediaElement.src = '';
mediaElement.remove();
mediaElement.srcObject = null;
@aussiedwarf aussiedwarf added the bug Something isn't working label Dec 2, 2024
Copy link
Contributor

github-actions bot commented Jan 2, 2025

Issues go stale after 30 days of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.

@github-actions github-actions bot added the stale label Jan 2, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
@mcottontensor mcottontensor self-assigned this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working never-stale
Projects
None yet
Development

No branches or pull requests

3 participants