Hi @vic.yang,
Regarding the ‘user deny screen share’ error, this issue only occurs when CPU and memory usage are too high. Since it happens rarely, we haven’t been able to consistently reproduce it for testing with the WebRTC official demo. If we encounter it again, we will try it. Could this be related to this issue, where high CPU and memory usage cause startShareScreen to take too long, triggering other events in between and resulting in the error—not directly caused by a user gesture?
Additionally, we are also facing a video freeze issue reported by our customer, but we don’t have a session ID for it. Here’s a related case: Canvas video occasionally freezes. Is there any solution or upgrade available to address this problem?
Thanks!