Open Bug 2014007 Opened 4 months ago Updated 3 months ago

webrtc/protocol/h264-profile-levels.https.html is timing out on android

Categories

(Core :: WebRTC: Signaling, defect, P3)

Product:
Core
Component:
WebRTC: Signaling
Type:
defect

Tracking

()

People

(Reporter: jib, Unassigned, NeedInfo)

References

(Depends on 1 open bug)

Details

webrtc/protocol/h264-profile-levels.https.html is timing out on android. Tests are already marked long.

On emulator? On real device?
I could imagine the Android encoder not handling the big frames we're feeding it.
We're running with media.navigator.streams.fake:true and constraints {width: 12800, height: 7200}. This should lead us to create 4096x2160 video frames. It could be the encoder dropping them, or it could be the emulator becoming very slow.

If it's due to encoder drops, root cause seems to be the same as for bug 2013936, i.e. that we don't care about h264 profile-level-id restrictions when setting up the encoder, and/or allowing any profile-level-id through the signaling layer.

Severity: -- → S3
Flags: needinfo?(jib)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.