See https://bugs.chromium.org/p/chromium/issues/detail?id=654701 for background /cc @yutakahirano @jakearchibald. Also #468 is kind of related, but that issue was about pipeTo which was confusing since pipeTo was under flux at the time.

A simple repro (run in Chrome) is

window.onunhandledrejection = e => {
  console.log(e.reason);
};

const rs = new ReadableStream({
  start(controller) {
    controller.close();
  }
});
const reader = rs.getReader();
reader.releaseLock();

This will log an unhandled rejection (and also show up in the console in Chrome, but that's a browser-specific devtools thing).

I think the correct solution is that all "state promises" like .closed should be marked as having their rejection handled (i.e. their [[PromiseIsHandled]] slot should be set to true).