New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 7 users

Issue metadata

Status: Assigned
Owner:
User never visited
Cc:
Components:
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

AppRTCDemo crashes in websocket based server

Reported by adamdev...@gmail.com, Dec 18 2014

Issue description

What steps will reproduce the problem?
1.AppRTCDemo with latest revision r7941
2.build and run
3.check "use websocket" and try loopback

What is the expected result?
works without error

What do you see instead?
It crashes with following error.
I attached log file.

What's more...
When i check websocket in setting, it doesn't work in some networks.(When click loopback, it stops in following)
12-18 13:42:50.382: D/RoomRTCClient(21433): Room response: {"params": {"asbr": "", "vrbr": "", "is_initiator": "true", "room_link": "https://3-dot-apprtc.appspot.com/room/19693200?hd=true", "audio_receive_codec": "", "pc_constraints": "{\"optional\": [{\"googImprovedWifiBwe\": true}]}", "include_vr_js": "", "media_constraints": "{\"audio\": true, \"video\": {\"optional\": [], \"mandatory\": {\"minWidth\": \"1280\", \"minHeight\": \"720\"}}}", "pc_config": "{\"iceServers\": [{\"urls\": \"stun:stun.l.google.com:19302\"}]}", "vsbr": "", "turn_url": "https://computeengineondemand.appspot.com/turn?username=46277754&key=4080218913", "wss_url": "wss://apprtc-ws.webrtc.org:8089/ws", "audio_send_codec": "", "include_loopback_js": "", "wss_post_url": "https://apprtc-ws.webrtc.org:8089", "room_id": "19693200", "meta_viewport": "", "arbr": "", "offer_constraints": "{\"optional\": [], \"mandatory\": {}}", "video_send_codec": "", "video_receive_codec": "", "opusfec": "true", "ssr": "", "client_id": "46277754", "error_messages": [], "stereo": "false", "is_loopback": "false", "messages": [], "opusmaxpbr": "", "vsibr": ""}, "result": "SUCCESS"}
12-18 13:42:50.382: D/RoomRTCClient(21433): RoomId: 19693200. ClientId: 46277754
12-18 13:42:50.382: D/RoomRTCClient(21433): Initiator: true
12-18 13:42:50.382: D/RoomRTCClient(21433): Room url: https://3-dot-apprtc.appspot.com
12-18 13:42:50.382: D/RoomRTCClient(21433): IceServer: stun:stun.l.google.com:19302[:]
12-18 13:42:50.382: D/RoomRTCClient(21433): Request TURN from: https://computeengineondemand.appspot.com/turn?username=46277754&key=4080218913
12-18 13:42:52.112: D/RoomRTCClient(21433): TURN response: {"username": "1418967771:46277754", "password": "fAb62sPNMXx4oOHQx1PB0c+4jA4=", "uris": ["turn:107.167.182.180:3478?transport=udp", "turn:107.167.182.180:3478?transport=tcp", "turn:107.167.182.180:3479?transport=udp", "turn:107.167.182.180:3479?transport=tcp"]}
12-18 13:42:52.122: D/RoomRTCClient(21433): TurnServer: turn:107.167.182.180:3478?transport=udp[1418967771:46277754:fAb62sPNMXx4oOHQx1PB0c+4jA4=]
12-18 13:42:52.122: D/RoomRTCClient(21433): TurnServer: turn:107.167.182.180:3478?transport=tcp[1418967771:46277754:fAb62sPNMXx4oOHQx1PB0c+4jA4=]
12-18 13:42:52.122: D/RoomRTCClient(21433): TurnServer: turn:107.167.182.180:3479?transport=udp[1418967771:46277754:fAb62sPNMXx4oOHQx1PB0c+4jA4=]
12-18 13:42:52.122: D/RoomRTCClient(21433): TurnServer: turn:107.167.182.180:3479?transport=tcp[1418967771:46277754:fAb62sPNMXx4oOHQx1PB0c+4jA4=]
12-18 13:42:52.122: D/RoomRTCClient(21433): pcConstraints: mandatory: [], optional: [googImprovedWifiBwe: true, DtlsSrtpKeyAgreement: false]
12-18 13:42:52.122: D/RoomRTCClient(21433): videoConstraints: mandatory: [minWidth: 1280, minHeight: 720], optional: []
12-18 13:42:52.122: D/RoomRTCClient(21433): audioConstraints: mandatory: [], optional: []
12-18 13:42:52.132: D/WSRTCClient(21433): Room connection completed.
12-18 13:42:52.132: D/WSChannelRTCClient(21433): Connecting WebSocket to: wss://apprtc-ws.webrtc.org:8089/ws. Post URL: https://apprtc-ws.webrtc.org:8089
12-18 13:42:52.132: D/de.tavendo.autobahn.WebSocketConnection(21433): WebSocket connection created.


What version of the product are you using? On what operating system?
r7941,
Ubuntu
Galaxy S5, Galaxy Note2
Android 5.0, Android 4.4

Please provide any additional information below.
I attached my built apk


 
AppRTCDemo-debug.apk
2.4 MB Download
log.txt
24.4 KB View Download
Project Member

Comment 1 by juberti@webrtc.org, Dec 19 2014

Cc: tkchin@webrtc.org
Labels: Area-SampleApps
Owner: jiayl@webrtc.org
Status: Assigned
Project Member

Comment 2 by jiayl@webrtc.org, Dec 19 2014

I cannot reproduce on my Nexus 5. 

The log does not contain a call stack. Can you get a call stack?
No i can only see fatal error that seems to be occured in .so.
I also tried latest version today but still same error in galaxy s5 and galaxy note 2.
Could you give me a hint how i can get a call stack?

Project Member

Comment 4 by jiayl@webrtc.org, Dec 19 2014

Run it in a debug session?
Yes the log was recorded in debug session.
First log is when device is connected in direct network and second log (attached log file) is when the device is in vpn network.
Project Member

Comment 7 by jiayl@webrtc.org, Dec 19 2014

Can you enable webrtc logging with instructions in https://code.google.com/p/webrtc/source/browse/trunk/talk/examples/android/README
Ok i will try and leave the result of it right away. Thank you.

Comment 9 Deleted

I attached two log files that was captured in debug mode. (ninja -C out/Debug)

One is when device is connected to vpn network.
The other is when device is connected to direct network.

In the past, with channel signalling server, AppRTCDemo worked in only direct network.
But now with websocket signalling server, it doesn't work in both vpn and direct network.

I expected it should work more correctly in direct server but once websocket conntected created, it gets closed after 1 min.
Take a look at the following log carefully in log_in_direct_network.txt
WebSocket connection created.
WebSocket connection closed.

Thank you.
log_in_direct network.txt
24.9 KB View Download
log_in_vpn.txt
44.4 KB View Download
Project Member

Comment 11 by jiayl@webrtc.org, Dec 22 2014

Cc: glaznev@webrtc.org juberti@webrtc.org phoglund@webrtc.org
The problem in 'direct network' seems a network connection issue. What do you see if you open https://apprtc-ws.webrtc.org:8089/ in a browser?

In the vpn network, the websocket is opened as expected and the crash seems unrelated to websocket. 
This error may be related:
12-22 01:27:16.736: E/libjingle(16850): Error(basicpacketsocketfactory.cc:56): UDP bind failed with error 99

But I cannot tell where the crash happens.

Adding a few more folks to get more ideas on how to get more information in this case.

- In direct network, it shows the following error code
 Mobile Chrome Browser: ERR_TUNNEL_CONNECTION_FAILED
 PC Chrome Browser: ERR_SSL_PROTOCOL_ERROR

- In vpn network, it shows Invalid Path
Project Member

Comment 13 by jiayl@webrtc.org, Dec 23 2014

OK, it seems that "direct network" is actually behind a proxy and the websocket server is unreachable.
In vpn network, the websocket server returns the expected response.
- Connection problem in direct network.
Yes, that's true, it's behind the proxy because in china, I can't connect to google directly.
And for more information, channel signalling server worked in proxy before.
Now only websocket signalling server doesn't work in proxy.

- Crash in vpn network.
Is there any update for crash error in vpn network?

Project Member

Comment 15 by juberti@webrtc.org, Dec 23 2014

jiayang, can we move the websocket port to 443? That should help this situation.
Project Member

Comment 16 by jiayl@webrtc.org, Dec 23 2014

Yes, let me do that.
Project Member

Comment 17 by jiayl@webrtc.org, Dec 23 2014

Re #14:- Crash in vpn network.
Is there any update for crash error in vpn network?

- No. There is not enough information to tell what's wrong. Can you reproduce the crash in Mobile Chrome?
I attached the screenshot in mobile chrome in both network.
I hope it will help you find the problem.
If you need more information please let me know.
Screenshot_2014-12-24-08-47-22.png
1.3 MB View Download
Screenshot_2014-12-24-08-49-04.png
1.2 MB View Download
any new update?
Project Member

Comment 20 by jiayl@webrtc.org, Dec 29 2014

The port change has landed. I'll push that to GAE today.
Project Member

Comment 21 by anatolid@webrtc.org, Nov 3 2016

This bus has not been modified for more than a year. Is this still a valid issue?
Project Member

Comment 22 by jansson@webrtc.org, Jun 9 2017

Components: Mobile
Project Member

Comment 23 by jansson@webrtc.org, Jun 9 2017

Components: -SampleApps

Sign in to add a comment