Please provide a sample testcase for the ease of triaging. 

I can repro for now only on very complex and not public url.

https://jsbin.com/tiyibabevo/3/edit?js,output is the nearest I can get
(sometimes there is huge "pauses" in the requestAnimationFram whereas in my case it total block)

'The play() request was interrupted by a call to pause()” error?' seems to be the culprit. so I'm fighting that in my js code for now.

Thank you for providing more feedback. Adding requester "ligimole@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

Thanks for the repro case.  However, it's not really clear how to use it.  Should I just run start_anew() from the console window to start the test?

sorry commented the call at the end for my sanity. 
just uncomment it should do the trick

note that it's a "heisenbug" as I surmise it implies race condition things, so it happens very randomly

Thanks for the info.  What's the expected output?  What I see is that its starts playing the song at time 0.  Then after 30 sec, it replays the song at around the 15 sec mark.  It does that for a few times and then plays at time 30 once, repeats the segment at time 45 sec several times before advancing to time 60.  And so on.

Is the repetition of the segments at starting at time 15 the issue?

It's supposed to play more or less seamlessly even if deleted/played
https://jsbin.com/zamuhugiga/edit?js,output

The Bug is when the requestAnimationFrame is not called any more for a long period, freezing the "progress bar visually after a restore. (and being silent a long time)

I do try to repro today but cannot it seems. 
(unless setting breakpoint in the try{}catch() which seems more consistent, but that doesn't really count)

Note that I fixed it in my app by making sure I never have any "DOMException: the play() request was interrupted by a call to a pause()" using lots of promises code checks.

So not sure if it's worth trying to fix it on your side.

I haven't seen any DOM exceptions here. I do hear glitches and silence, but the silence might be because it's reached the end of the song.  (I'm not constantly listening to the test.)

Sorry, I think yesterday link copy/paste from jsbin was no good, just checked, there is no try nor play/pause dom. 
The last link shared using the jsbin "share" do work. (tested in a "private" tab): https://jsbin.com/zamuhugiga/edit?js,output 

As said in last comment today, I have it no more since I avoid all DomException in my app code, that do point at my code being faulty not avoiding that. I wasn't doing things correctly rather than bug on your side, sorry to have bothered you.

Ok.  I'll leave this open for a bit longer in case you find something new.

Since play() returns a promise, I would certainly use that to make sure play has started before proceeding with further processing.

No further comments.  Closing as WontFix (cannot reproduce).

If you come across this problem again, please reopen this or file a new bug (with component Blink>WebAudio)