M122 Release Notes

1,378 views
Skip to first unread message

Harald Alvestrand

unread,
Feb 13, 2024, 5:39:47 AMFeb 13
to discuss...@googlegroups.com

WebRTC M122 is going to be released as part of Chrome M122, currently planned for release on February 20, 2024.


We had one PSA for M122:

and one new feature is shipping:


The following issues were marked as fixed or verified and had at least one commit in M122 (build, test and trivial code changes are not included):


Issue

Summary

Component

webrtc:15145

SDP offer with m-line not containing unsupported video codec results in error

PeerConnection

webrtc:15661

ByteBufferReader should use uint8_t not char

Internals

chromium:1512631

Cloned encoded video frames have RTP retransmission disabled

Blink>WebRTC

>PeerConnection

webrtc:15770

getStats local-candidate url is missing hostname in some cases and IPv6 hostnames lack []

PeerConnection

webrtc:15713

Hitting CHECK in H264 Processing

Video

webrtc:15164

Replace use of RTCStatsMember<T> with absl::optional<T> instead

Stats

chromium:1508337

Cloning RTCEncodedAudioFrames drops CSRCs

Blink>WebRTC

>PeerConnection

webrtc:15656

Unify plumbering of widely used components.

Internals

webrtc:15704

Rename "metronome" to "decode_metronome"

PeerConnection

webrtc:9987

Clean up WebRTC threading

Internals

webrtc:15574

Consider how "No media" is signalled when creating a PeerConnection

Cleanup

chromium:1354491

Make the TaskQueuePacedSender bursty.

Blink>WebRTC

>PeerConnection

chromium:1486851

CGDisplayStreamCreate() in macOS media picker

Blink>GetDisplayMedia

chromium:1375217

tracking bug for webrtc-internals ui/ux improvements

Blink>WebRTC>Tools

chromium:1354101

RTCRtpSender setParameters() extensions for requesting the generation of a key frame

Blink>WebRTC

>PeerConnection

chromium:822696

Deprecate and remove legacy getStats() API (the non-standard callback-based one)

Blink>WebRTC

>PeerConnection

chromium:1297521

Track WebRTC FrameBuffer Field Trial Rollout

Blink>WebRTC>Video


For the full list of commits please refer to the git log between this branch and the previous branch. See here for a description of what the release notes contain.


We strongly recommend WebRTC developers to fully test their services in Chrome Beta to ensure stability for end-users.

 

The Chrome release schedule can be found here.


These release notes were prepared by Philipp Hancke.


Reply all
Reply to author
Forward
0 new messages