See: https://github.com/WebAudio/web-audio-api/issues/1515#issuecomment-381277112

This is a problem, but we don't know how to fix it yet. I would like to label this as "ExternalDependency".

The NextAction date has arrived: 2018-04-20

IMO throwing an error in AWGS does not anything, so I will change the status. Perhaps I won't start to work on it unless we have the spec-level solution for this.

Also removing the "blocking" tag from this issue.

But we can certainly do the check now.  And we can print a console message right?  Spec doesn't forbid that.

And then what can we print? A warning or an error?

Isn't it an error?  How are you supposed to continue when you've mangled the output array?

Since the behavior for such case is unspecified, anything can be done.

1. Do nothing and produce silence.
2. Do nothing and produce silence. Mark the processor as "inactive".
3. Throw an exception and stop.
4. Warn user and ignore the array for the current render quantum.
5. Do nothing at all.
6. so on...

It is a bit sad we can do basic things like this properly because the WGS doesn't support it.

Producing silence is not doing nothing. :-)

At this point, I don't care too much about exactly what happens except that we should print out something (warning or error or info) to the dev console that something unexpected happened.