[whatwg/streams] Should terminating a worker close/error streams? (Issue #1256)

I found that Firefox currently explicitly closes `new Response(...).body` when the owning worker closes: https://searchfox.org/mozilla-central/rev/9de332d5c8faac58dc1232b8a6383ce6cb1400f4/dom/base/BodyStream.cpp#169

But for general streams AFAICT both Firefox and Chrome do not close nor error the stream, and just let the read requests stall forever when trying to read streams transferred from terminated workers.

But should worker termination ping the streams what's happening? This will expose worker GC, but Web Locks already exposes that information.

cc @asutherland

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1256
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1256@github.com>