Closed Bug 1296002 Opened 9 years ago Closed 9 years ago

(android-only) OpenH264 webrtc calls aren't working in 48 and 49

Categories

(Core :: WebRTC, defect, P1)

Product:
Core
Component:
WebRTC
Platform:
Unspecified
Android
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox48 --- affected
firefox49 --- affected
firefox50 --- unaffected
firefox51 --- unaffected

People

(Reporter: jesup, Assigned: dminor)

Details

Note: fails on 48/Release with 1.5.3 and on 49/DevEd 1.6 It works with 50 and 51 with 1.6 I presume this is something fixed (somehow) in 50, but it's unclear that that would be and why it's Android-specific. (GMP change?) Also, since it was known to work in older releases, where did it regress? It appears to be on the encoding/sending side. Note: for testing, generate a new profile and then start Firefox and wait ~ 2 minutes; you can see if it's downloaded and the version in Menu->Tools->AddOns. To generate a new profile, I uninstall and re-install
Summary: OpenH264 webrtc calls aren't working in 48 and 49 → OpenH264 webrtc calls aren't working in 48 and 49 (android-only)
Rank: 10
Summary: OpenH264 webrtc calls aren't working in 48 and 49 (android-only) → (android-only) OpenH264 webrtc calls aren't working in 48 and 49
Assignee: nobody → rjesup
Assignee: rjesup → dminor
Very rough regression range (narrows it down to a month or so!): https://hg.mozilla.org/mozilla-central/rev/e99061fde28a is broken https://hg.mozilla.org/mozilla-central/rev/57fa89168a44 works
This is working for me in on a nexus 6 in 48.0 with 1.5.3 and in 49.0b11 with 1.6, testing on the webrtc landing page (https://mozilla.github.io/webrtc-landing/pc_test.html with the "require H.264" flag checked). This is difficult to test as you definitely need to wait a good two minutes after generating a new profile before attempting a call or it will appear to be broken. Strangely, it looks like the H.264 plugin will appear in AddOns before a call can be successfully made. I've gone down a few rabbit holes attempting to bisect this only to find that my "broken" build was actually working on subsequent retesting, presumably because I didn't wait long enough before attempting a call. Some possibilities: * the webrtc landing site isn't sufficient to test this * it works on my device by not others * it fails intermittently Unless one of those is potentially the case, I think this is a WORKSFORME.
Flags: needinfo?(rjesup)
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(rjesup)
Resolution: --- → WORKSFORME

Removing regressionwindow-wanted keyword because this bug has been resolved.

Keywords: regressionwindow-wanted

Removing regressionwindow-wanted keyword because this bug has been resolved.

Removing regressionwindow-wanted keyword because this bug has been resolved.

You need to log in before you can comment on or make changes to this bug.