You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Start the signaling server
Start UE and connect Pixelstreaming to the SS
Start the stresstest
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
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.
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:
Expected behavior
Platform (please complete the following information):
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.
The text was updated successfully, but these errors were encountered: