Tried testing the issue on reported chrome version #72.0.3607.0 using Windows 7 and Windows 10 by following steps as per comment#0. The following are the observation noted while testing the issue.

Observations:
===========
1.The sequence of function calls: play(), stop(), play(), stop(), with about 1 second passing between one call and other.
2.The play function increases the volume and when stop is called the value drops to "0".
3.The current volume increases with 1 second when play() function gets called.

Attached screencast for reference.
@reporter: Could you please provide the screenshot or screencast of the issue so that it would be really helpful for further triaging of the issue.
Thanks.!

Deleted: 904244.mp4 7.6 MB

	904244.mp4 7.6 MB View Download

What for? Your screencast shows the values don't change continuously.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Able to reproduce the issue on reported chrome version 72.0.3607.0 also on latest chrome 72.0.3616.0 using Ubuntu 17.10 and Windows 10.  

Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged.

Note: observed different behavior on Mac

Thanks! 

I hear the some pops in the audio.

I think this snippet (use hoch.github.io/canopy) shows the problem:

// @sampleRate 48000
// @duration 10
// @channels 1

var oscillator = context.createOscillator();
var fader = context.createGain();
oscillator.connect(fader);
fader.connect(context.destination);

oscillator.frequency.value = 440;
fader.gain.value = 0;
oscillator.start(0);

var FADE_TIME = 2; //seconds
var PLAY_STOP_CYCLE_INTERVAL = 1; //how often to change between play (fade-in) and stop (fade-out)
var LOGGING_INTERVAL = 0.05; //seconds
var MAX_PLAY_STOP_CYCLES = 2;

let playing = false;
for (let k = 0; k < 10; ++k) {
    if (!playing) {
	context.suspend(k)
	    .then(() => {
		    time = context.currentTime;
		    fader.gain.cancelAndHoldAtTime(time);
		    fader.gain.linearRampToValueAtTime(1, time + FADE_TIME)
			})
	    .then(() => context.resume());
    } else {
	context.suspend(k)
	    .then(() => {
		    time = context.currentTime;
		    fader.gain.cancelAndHoldAtTime(time);
		    fader.gain.linearRampToValueAtTime(0, time + FADE_TIME)
			})
	    .then(() => context.resume());
    }
    playing = !playing;
}


At time 1, the ramp up is half done, and we cancel the running event and ramp down.  This is ok.

At time 2, we should cancel the event (ramp down) and start ramping up again.  However, at time 2, we didn't hold the output; it starts at 0 for some reason.  But we ramp up as expected.

At time 3, we cancel and start ramping down.  But instead of holding, the output appears to be 0 already, so ramping down to 0 does nothing.

Assuming the snipped is doing what I think it should be, we can see there's a problem in cancelAndHold, at least at time 2.  Not sure what's happening at time 3.