3.9.7 1636
Chromium 65.0.3325.181

This bug has been present for a long time across all versions of Chromium, I just never realized it was FDM causing it. I finally decided to troubleshoot it, and was kinda shocked FDM was the culprit.

Basically, FDM's integrated extension causes some pretty terrible audio bugs in certain scenarios. Triple-click "select line" (on some elements at least), causes the html5 audio to duplicate and restart alongside the initial audio. Triple-clicking again causes a third instance of the audio, and so forth.

I think this is a decent example: http://www.worldstarhiphop.com/videos/v ... 1YoHUg7Z60

Triple-click the video title.

anagrammar wrote:3.9.7 1636
Chromium 65.0.3325.181

This bug has been present for a long time across all versions of Chromium, I just never realized it was FDM causing it. I finally decided to troubleshoot it, and was kinda shocked FDM was the culprit.

Basically, FDM's integrated extension causes some pretty terrible audio bugs in certain scenarios. Triple-click "select line" (on some elements at least), causes the html5 audio to duplicate and restart alongside the initial audio. Triple-clicking again causes a third instance of the audio, and so forth.

I think this is a decent example: http://www.worldstarhiphop.com/videos/v ... 1YoHUg7Z60

Triple-click the video title.

Hi,

Chromium isn't officially supported in FDM, so it depends on which version of the extension you have.
it's not clear how you try to download, can you send us a video of the process step by step?

"All versions of Chromium" includes Google Chrome, which is supposedly supported, no? If you followed the simple steps of clicking on the link provided, and triple-clicking the title on that page, I can't imagine you wouldn't be able to repro this bug.

This bug has been around forever. I assumed it was a browser bug, and since the steps which cause it aren't something I do consistently every day, I ignored it for a long time. I do however, encounter it often enough that I'd finally had enough, and became determined to figure out the cause. It is FDM, without a doubt.

I made a screen record with audio to demonstrate the bug. I used a fresh install of Google Chrome with only FDM installed. A bug like this is indicative of some pretty terrible coding, and it's annoying as all hell, so I hope you won't dismiss it as not "officially supported", when it clearly is an issue in officially supported browsers.

https://www.youtube.com/watch?v=hEGqJXK ... e=youtu.be

The devs told me that the have indeed identified the bug and are working on it.

Sounds like good news. I've been checking the last couple days, but no updates. Any ETA on the bug fix?

All I know is that it's on the list.

Seems I was overly optimistic thinking they'd push a bug-fix within a couple days. Been more than a couple weeks now, and still nothing, which is pretty disappointing.

It's taking longer than expected, sorry.

The problematic code is in . It's the first function at line 13. Chrome and Firefox are both affected, and it seems to be a browser bug more than anything being wrong in the code. A bug report is filed for Chromium: https://bugs.chromium.org/p/chromium/is ... ?id=847006

This is an edge-case, so I don't expect it to get a ton of attention anytime soon. In the meantime, I really hope you can rewrite the function to work around the bug. In the newest Chromium stable, I find it a little more difficult to repro consistently, but it's far worse when it occurs. Now multiple audio instances are cloned, and they're echoed and distorted.

Really? I saw you pushed an update today, so I downloaded the source and checked the diff on that file. You guys rewrote a bunch of Youtube functions and left the one causing the bug exactly the way it was. Great job guys!