- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Tue, 08 Jul 2025 23:32:47 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc: == Prevent GC of non-closed RTCDataChannels in workers == In https://github.com/w3c/webrtc-pc/pull/2902 we added a connection.[[[DataChannels]]](https://w3c.github.io/webrtc-pc/#ref-for-dfn-datachannels-1) internal slot to keep `RTCDataChannel`s from being GC'ed on main-thread. But nothing keeps them alive once transferred to workers. This seems like an omission as transfer was added later, so we should add some language to ensure that. Also the RTCDataChannel [transfer steps](https://w3c.github.io/webrtc-pc/#transfering-a-data-channel) sets _"value.[[ReadyState]] to "closed"."_ so the detached main-thread object left behind on main-thread after transfer in connection.[[[DataChannels]]](https://w3c.github.io/webrtc-pc/#ref-for-dfn-datachannels-1) is closed, which seems a bit surprising. Let's clean that up. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3062 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 July 2025 23:32:48 UTC