Using the per-revision bisect providing the bisect results,
Good Build: 55.0.2875.0 (revision :421703)
Bad Build:  55.0.2876.0 (revision :421986)
 
You are probably looking for a change made after 421808 (known good), but no later than 421809 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/b0a6d1d8932f6d5a1bbdfb4a650e139d6557163c..963e02b239af92fa00c6505ee29400bfc13b8a70

From the above CL , could anyone help us to find the actual suspect and in assigning it to the concern owner.

Thanks!

I doubt it is franzih@'s change. Jakob, is it possible that JavaScript behavior changed?

Able to reproduce locally, but only repeating the steps a couple of times. Will take a look.

The bisect seems to be wrong. Locally I'm getting the following:

55.0.2883.87 bad
55.0.2880.0 bad
55.0.2879.0 bad
55.0.2877.0 bad <- culprit

55.0.2876.0 good
55.0.2875.0 good

Note that our archived google-chrome-stable-55.0.2877.0-1.x86_64.rpm build actually contains 55.0.2883.87 (chrome://version).

Chrome-TE, could you please do a narrower bisect.

In the range  https://chromium.googlesource.com/chromium/src/+/b121dd8b9380574db8d6ebee851c1dfd61369cda looks interesting.

Able to reproduce the issue on Windows 7, Mac 10.12.2 and Linux Ubuntu-14.04 using chrome stable version #55.0.2883.87 and latest canary #57.0.2984.0

Bisect Information:
=====================
Good build: 55.0.2875.0  Revision(421703)
Bad Build : 55.0.2876.0  Revision(421986)

Change Log URL:
https://chromium.googlesource.com/chromium/src/+log/509bf6e55d629763e4ba67a123c575de1d60c686..ce8199558bd1cc8737c4349fc0937860b380da3c

Review-Url: https://codereview.chromium.org/2371993003

Thanks...!!

This was fixed. I can reproduce on 56.0.2924.51 but it seems to work fine on trunk (57.0.2986.0).

Marking as WontFix. Please reopen if you can reproduce on 57.0.2986.0 or later. Can you also check the latest Beta?

#7, FYI: Sometimes it takes quite a few back-and-forths between the audio/video radio button and frequent clicking on mute buttons to reproduce.

I can still repro on 

Google Chrome	57.0.2985.0 (Official Build) beta (64-bit)

That's the latest build I could find available for download.

Steps: 
1. Open page.
2. Start playing video.
3. Mute.
4. Switch to audio radio button.
5. Play audio.
6. Mute.
7. Switch back and forth between audio and video, toggle mute a couple of times on each page, toggle audio playback.
8. Repeat 7. for a minute or so until mute gets stuck.

Also reproduces on Google Chrome 57.0.2986.0 (Official Build) beta (64-bit).

I'm trying to reproduce this on 58.0.3013.3 and I can't. Can you check if you are still able to reproduce this issue?

Can't repro either anymore on 58.0.3013.3.