Tested the issue in Android and could not reproduce the issue.

Steps Followed:
1. Launched Browser 
2. Logged in FB with valid credentials
3. Played a video
4. Did not hear any noise

Chrome versions tested:
63.0.3239.111

OS
Android 7.0.0

Android Devices
7.0.0; SM-J710F Build/NRD90M

@park: Could you please update your Chrome to the latest version #63.0.3239.111 and check if you still face the issue? If so help us with the details of your device and a the sample video where you're seeing the issue.

Thanks!!

Dear Chrome team

It's reproducible on 63.0.3239.111.
Could you double-check it with a reproducible url : https://m.facebook.com/jtbcnews/?tsid=0.06808807465991151&source=result?

Thanks.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue in Android and could reproduce the issue. Heard the electrical sounds on playing the video.

Steps Followed:
1. Launched Chrome .
2. Navigated to  https://m.facebook.com/jtbcnews/?tsid=0.06808807465991151&source=result?.
3. Heard the electrical sounds on playing the video.


Chrome versions tested:
63.0.3239.111, 65.0.3312.0

OS
Android 7.0.0

Android Devices
Samsung J7

Considering this issue as Non-Regression issue as observing same behavior since M55.

Please navigate to below link for and video & log's --
go/chrome-androidlogs/796028

sandeepkumars@ can you double confirm that you saw this issue on 65.0.3312.0? That should have the fix for out of range float values.

 Issue 789208  has been merged into this issue.

Seems to be happening on a few devices. I can reproduce on my Pixel2 XL w/ the clip here https://drive.google.com/file/d/1Vo4sO9NzNrLX4hD-0_BP0K-2ee1qGTbq/view?usp=sharing  @ 1m3s  (sorry internal only link).

It doesn't reproduce on desktop; given issue 780123 it seems likely ffmpeg's decoding on ARM is going awry and generating garbage values at this point. I'll send it along to upstream as well to see if anything stands out to them.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/eb53b52399f5b46426202f77a12dba3fe822ee09

commit eb53b52399f5b46426202f77a12dba3fe822ee09
Author: Ted Meyer <tmathmeyer@chromium.org>
Date: Thu Jan 11 01:54:39 2018

Temporary fix for crbug/796028

It seems there is an issue with the apply noise functions, however they
are hand optomized ARM assembly, and more digging will be required to
diagnose the true root cause of this issue.

Bug:  796028 
Test: Manually
Change-Id: I2babbdfc7c015d2e37c5385b896714d6787ccb0f
Reviewed-on: https://chromium-review.googlesource.com/861244
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>

[modify] https://crrev.com/eb53b52399f5b46426202f77a12dba3fe822ee09/libavcodec/arm/sbrdsp_init_arm.c
[modify] https://crrev.com/eb53b52399f5b46426202f77a12dba3fe822ee09/chromium/patches/README

Seems this is being encountered more and more on Facebook AAC encodes, we've got 3 separate bugs (1 internal) on this, so marking as RBS - fix is simply to disable NEON optimizations for a couple functions.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/36f3756b89b88bbd9b3002c17a92375237fe5e6d

commit 36f3756b89b88bbd9b3002c17a92375237fe5e6d
Author: Dale Curtis <dalecurtis@chromium.org>
Date: Thu Jan 11 03:21:23 2018

Roll src/third_party/ffmpeg/ 423f74fab..eb53b5239 (2 commits)

https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/423f74fab02f..eb53b52399f5

$ git log 423f74fab..eb53b5239 --date=short --no-merges --format='%ad %ae %s'
2018-01-10 tmathmeyer Temporary fix for crbug/796028
2017-12-18 dpranke Change the way the ffmpeg_branding gets its defaults.

Created with:
  roll-dep src/third_party/ffmpeg

BUG= 796028 
TEST=no screeching
TBR=sandersd

Change-Id: Ibc997fb350611069bf8d9de8a378bba851047d8f
Reviewed-on: https://chromium-review.googlesource.com/860169
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#528548}
[modify] https://crrev.com/36f3756b89b88bbd9b3002c17a92375237fe5e6d/DEPS

In response to comment #6.

Tested the issue using #65.0.3317.0 on Android 7.0.0; SM-J710F Build/NRD90M and can still hear the electrical sounds on playing videos from https://m.facebook.com/jtbcnews/?tsid=0.06808807465991151&source=result?.

Thanks!!

I am still able to reproduce the issue in latest version of chrome.

That fix won't be available until tomorrow in 65.0.3319.0

Verified in 65.0.3319.0 that the issue is fixed. Requesting merge for DEPS update to M64 for ffmpeg, which pulls in https://crrev.com/eb53b52399f5b46426202f77a12dba3fe822ee09 which just disables NEON optimizations for this piece of AAC decoding. No power or performance change shown in perf charts:

https://chromeperf.appspot.com/report?sid=f0738dc39bcda5e860dad79cf138f1e8791cdc4036ed9ef0736a8bf4d9be2fa2

This bug requires manual review: We are only 10 days from stable.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/d3f81700982851914e334ba680bf4613263de293

commit d3f81700982851914e334ba680bf4613263de293
Author: Dale Curtis <dalecurtis@chromium.org>
Date: Tue Jan 16 21:26:26 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/b7b7b5255649dab1b10b7d3c7a8e0f46918d6682

commit b7b7b5255649dab1b10b7d3c7a8e0f46918d6682
Author: Ted Meyer <tmathmeyer@chromium.org>
Date: Wed Jan 17 20:10:45 2018

Revert "Temporary fix for crbug/796028"

This reverts commit eb53b52399f5b46426202f77a12dba3fe822ee09.

Reason for revert: Applying better fix from upstream

Original change's description:
> Temporary fix for crbug/796028
> 
> It seems there is an issue with the apply noise functions, however they
> are hand optomized ARM assembly, and more digging will be required to
> diagnose the true root cause of this issue.
> 
> Bug:  796028 
> Test: Manually
> Change-Id: I2babbdfc7c015d2e37c5385b896714d6787ccb0f
> Reviewed-on: https://chromium-review.googlesource.com/861244
> Reviewed-by: Dale Curtis <dalecurtis@chromium.org>

TBR=dalecurtis@chromium.org,tmathmeyer@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug:  796028 
Change-Id: If7369ce09efb5cecc5e24a68a02bf611ef5fce43
Reviewed-on: https://chromium-review.googlesource.com/871371
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>

[modify] https://crrev.com/b7b7b5255649dab1b10b7d3c7a8e0f46918d6682/libavcodec/arm/sbrdsp_init_arm.c
[modify] https://crrev.com/b7b7b5255649dab1b10b7d3c7a8e0f46918d6682/chromium/patches/README

Dear Chrome team,
As the fix in comment 11, hopefully I expect a new fix will be landed soon.
Could you let me posted with a new fix?

We merged the upstream fix with https://chromium.googlesource.com/chromium/src/+/4ffbc3f1ff2f14467091b076f40964ba0b63a756 which is 65.0.3325.0+

 Issue 804259  has been merged into this issue.

Verified on Chrome:65.0.3325.16 Device:Pixel/NJH47F with the URL mentioned in C#3

Dear Chrome team, kindly pinging.

This has been resolved. I'm not sure what you're pinging about?

 dalecur...@, sorry for false alarm and verified it's already fixed.