The calls to RTCRtpSender.setParameters() are all chained and the current maxHeight is set after the call to setParameters is resolved. If there is another call made to setParameters before the previous one resolves, we can end up passing the wrong maxHeight resulting in the client getting stuck at an unexpected resolution. This issue can be reproduced sometimes when the users are moving across the main and breakout rooms. TPC.setVideoCodecs() ends up pushing a wrong maxHeight for update when the previous call to setParameters hasn't resolved yet.release-8443
|
|
||
2057 |
|
2057 |
|
2058 |
|
2058 |
|
2059 |
|
2059 |
|
|
2060 |
|
|
|
2061 |
|
|
2060 |
|
2062 |
|
2061 |
|
2063 |
|
2062 |
|
|
|
2063 |
|
|
|
2064 |
|
2064 |
|
2065 |
|
2065 |
|
2066 |
|
2066 |
|
|
|
||
2125 |
|
2125 |
|
2126 |
|
2126 |
|
2127 |
|
2127 |
|
2128 |
|
|
|
2129 |
|
2128 |
|
2130 |
|
2129 |
|
2131 |
|
2130 |
|
|
|
||
2197 |
|
2196 |
|
2198 |
|
2197 |
|
2199 |
|
2198 |
|
2200 |
|
|
|
2201 |
|
|
|
2202 |
|
2199 |
|
2203 |
|
2200 |
|
2204 |
|
2201 |
|
2205 |
|
2202 |
|
2206 |
|
2203 |
|
2207 |
|
2204 |
|
2208 |
|
|
|
2209 |
|
2205 |
|
2210 |
|
2206 |
|
2211 |
|
2207 |
|