[BUG] PixelStreaming ueApp on Chrome and Edge is crashed !!!

General Feedback & Requests
1

谷歌浏览器升级
chrome is updated
webRtc 适配器的js 也升级了
webRtc adapter.js is updated
在四天前？？？
4 days ago??
我的虚幻应用全部挂了。。。
my ueApp is all crashed
你可以看图片
you can see the pictures
或者
OR



[2021.03.14-08.36.47:105][561]PixelStreamingWebRTC: Error: (webrtcsdp.cc:370): Failed to parse: "a=extmap-allow-mixed". Reason: Expects at least 2 fields.
[2021.03.14-08.36.47:106][561]LogPixelStreamingSS: Error: Failed to parse answer's SDP
v=0
o=- 7973411689470192125 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE 0 1 2
a=extmap-allow-mixed
a=msid-semantic: WMS
m=audio 9 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 110 112 113 126
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrago:3C9
a=ice-pwd:daepUFvey0DnmmG6p0MyLYAD
a=ice-options:trickle
a=fingerprint:sha-256 CC:59:31:A8:49:89:23:36:47:68:F7:E0:42:D2:49:41:D1:3F:34:6C:56:94:5C:8A:28:8F:B5:07:BA:B9:9D:5E
a=setup:actpass
a=mid:0
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id
a=recvonly
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmt[2021.03.14-08.36.47:171][565]LogPixelStreamingSS: Connection to SS closed:
status 1000
reason: Successfully closed connection to our peer
was clean: 1
[2021.03.14-08.36.47:171][565]LogPixelStreamingSS: Connecting to SS ws://192.168.0.109:26213
[2021.03.14-08.36.47:173][565]LogWebSockets: Warning: FLwsWebSocket[1]::Close: Already closing, ignoring subsequent attempt
[2021.03.14-08.36.47:238][569]LogPixelStreamingSS: Connected to SS
[2021.03.14-08.36.47:271][571]LogPixelStreamingSS: <- SS: {"type":"config","peerConnectionOptions":{"iceServers":{"urls":"stun:123.56.11.94:19302"]}]}}

我不知道该怎么办了？
I don’t know how can I do
在中国 搜狗浏览器和360浏览器 是可以正常使用的
sougo web browser and 360 web browser is can be used in China

2

The occurs in the SDP parser on encountering a=exmap-allow-mixed.

This is a known bug in the WebRtc parser used by Chromium, and so Chrome and supposedly Edge (but not Firefox).

Chromium has added a flag offerExtmapAllowMixed that can be turned off to prevent the browser including this attribute.

https://groups.google.com/a/chromium.org/g/blink-dev/c/7z3uvp0-ZAc/m/8Z7qpp71BgAJ

The flag would be unset in the RTCConfiguration, which is passed to the RTCPeerConnection constructor.

For example, by adding the line,

self.cfg.offerExtmapAllowMixed = false;

to createOffer in webRtcPlayer.js, like so,

this.createOffer = function() {
	if(self.pcClient){
		console.log("Closing existing PeerConnection")
		self.pcClient.close();
		self.pcClient = null;
	}
	self.cfg.offerExtmapAllowMixed = false;
	self.pcClient = new RTCPeerConnection(self.cfg);
	setupPeerConnection(self.pcClient);
	self.dcClient = setupDataChannel(self.pcClient, 'cirrus', self.dataChannelOptions);
	handleCreateOffer(self.pcClient);
};

Be aware that the Chromium team intends to deprecate the flag.

If they do this before Epic updates the version of WebRtc provided with the PixelStreaming plugin, you may need to munge the SDP to remove the attribute. (Not a Guide to SDP Munging - webrtcHacks)

1 Like