1305014 - Crash in mozilla::OpenSLESProvider::RealizeEngine

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: Audio/Video, defect)

Description

[Teodora Vermesan (:TeoVermesan)]

This bug was filed from the Socorro interface and is 
report bp-a9d7afd7-d620-4d20-9cf3-145352160923.
=============================================================

Steps to reproduce:
1. Go to Go http://mozilla.github.io/webrtc-landing/gum_test.html
2. Choose Audio & Video

Expected results:
- A permission prompt should appear asking to access the built-in camera and built-in microphone

Actual results:
- Nightly crashes

Comment 1

[Alex Caziuc]

Regression window:

good build:2016-09-21
bad build:2016-09-22

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e2d2897e4a7449759267bf168e6b37f7b8c3a94b&tochange=f0e6cc6360213ba21fd98c887b55fce5c680df68

Comment 2

[Paul Adenot (:padenot)]

What device is that? On my Sony Z5C, latest Nightly it works as intended.

Comment 3

[Gian-Carlo Pascutto [:gcp]]

From the linked crash report:

Android Manufacturer 	
OnePlus

Android Model 	
ONE A2001

Comment 4

[Paul Adenot (:padenot)]

Alex, don't you have a OnePlus ?

Comment 5

[Teodora Vermesan (:TeoVermesan)]

First time you choose "Audio & Video", Nightly crashes and after restarting the browser and choose once again "Audio & Video", accept permissions, the following error message is displayed: "NotReadableError: Failed to allocate videosource".
I could also reproduce the issue on: Samsung Galaxy Note 5 (Android 6.0.1) and Samsung S6Edge (Android 6.0)

Comment 6

[Gian-Carlo Pascutto [:gcp]]

Does the crash produce with audio only? Video is broken due to bug 1304975.

Comment 7

[Teodora Vermesan (:TeoVermesan)]

I cannot reproduce the crash by choosing "Audio".

Comment 8

[Alex Chronopoulos [:achronop]]

Yes, and I crash too but in a different way:

The 1st time I choose Audio & Video I get the prompt and when I choose to share I get an error message:" NotReadableError: Failed to allocate videosource"
I refresh the page to go back to the initial menu and then when I press again Audio & Video for 2nd time I crash.

Comment 9

[Gian-Carlo Pascutto [:gcp]]

Okay, that explains the regression range:

	c1e0b205c39b	Florian Quèze — Bug 1299783 - change the name of the temporary permission from 'camera' to something not exposed in the UI, r=gcp.

This change broke video.

However, that's all a bit of a red herring. What we're seeing is that if video fails, we're doing something wrong with the audio setup that eventually causes OpenSLES to crash.

Comment 10

[Alex Chronopoulos [:achronop]]

I am preparing a patch with Full Duplex in opensl es. That changes a little (the least possible) the audio playback. We can follow the error after full duplex is landed. It's a big patch so we may see more errors than that :)

Comment 11

[Ryan VanderMeulen (PTO, back July 27)]

Is that work happening in another bug we can follow along in? We're a couple weeks away from the next uplift and it would be nice if this didn't ride the trains with it.

Comment 12

[Alex Chronopoulos [:achronop]]

The work mentioned earlier was the full duplex back end for android and it is happening in Bug 1221574. I test with a custom fennec including the changes from that bug and seems to work just fine. But, it also works with latest nightly so it should bee something else which has been fixed in the meantime. If it works for Teodora too we can close the bug.

Comment 13

[u549602]

Hi Alex,

I am providing information on behalf of Teo,i can confirm that the crash is no longer reproducible by following the steps in the description and comments. This issue seems to be fixed, tried on a Samsung Galaxy S6 EDGE (Android 6.0) and on a Samsung Galaxy Note 5 (Android 6.0.1). This issue was tested using the 52.0a1 (2016-10-21)build

Comment 14

[Alex Chronopoulos [:achronop]]

I close it for now since it is not reproducible any more, feel free to reopen if the error returns.