According to @bakulf Mozilla will not deliver a message when an object cannot be deserialized in a particular realm, e.g., ArrayBuffer's allocation exception. Instead, for workers anyway, the exception will go to onerror.

Perhaps we should specify, maybe as part of #935, that some special error message gets delivered instead. E.g., we could set data to the exception thrown or set data to null and expose the exception separately. That way you don't get a global exception you don't know the origin of but instead a message you were expecting, just without the data to a problem.

This is also important for SharedArrayBuffer as I understand it.

@lars-t-hansen, @pizlonator, and @ajklein might have thoughts.