New issue
Advanced search Search tips

Issue 842921 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

AudioContext resume promise doesn't resolve or reject when audio is locked

Reported by ja...@goldfirestudios.com, May 14 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Run the provided test case without performing any user interactions on the page (also at https://codepen.io/goldfire/pen/MGBVGE).

What is the expected behavior?
The AudioContext.resume promise should either resolve or reject.

What went wrong?
Nothing happens, the promise just hangs without ever returning. This makes it impossible to know that the audio is locked.

Did this work before? Yes 65

Does this work in other browsers? Yes

Chrome version: 66.0.3359.139  Channel: stable
OS Version: OS X 10.13.4
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M66
Cc: phanindra.mandapaka@chromium.org
Components: Blink>Compositing
Labels: -Needs-Bisect Triaged-ET hasbisect
Mergedinto: 841933
Status: Duplicate (was: Unconfirmed)
Able to reproduce the issue on reported version 66.0.3359.139 using Mac 10.12.6,Ubuntu 14.04 and Win10, this issue is not observed on latest chrome M68 #68.0.3430.0 and hence providing reverse bisect information below.

Bisect Info:
================
Good build: 68.0.3428.0
Bad build: 68.0.3427.0 

You are probably looking for a change made after 557940 (known good), but no later than 557955 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/e45bf8e41c7786a1592ff3ab8e259e39dded76d4..de4c73a8e0c0db48fb441eb8531145db07d3401e

suspect: https://chromium.googlesource.com/chromium/src/+/70f5eed34d513d3c8d35cf5bb6d4a59b46511159

Reviewed-on: https://chromium-review.googlesource.com/1054433


The issue looks similar to  issue 841933 and is already fixed in canary, hence, merging into issue id 841933. Fix should be available in M-66 soon.

Thanks!
This stopped working again. Calling resume now just throws "The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page." in the console and still doesn't resume/reject.
I've created a new issue at https://bugs.chromium.org/p/chromium/issues/detail?id=884337 since I assume this will never again be seen.

Sign in to add a comment