search

peers / peerjs

Simple peer-to-peer with WebRTC.
https://peerjs.com
MIT License
12.46k stars 1.43k forks source link

Video chat example crashes on Android Chrome beta (32.0.1700.58) #137

Closed demobo-com closed 5 years ago

demobo-com commented 10 years ago

Video chat example crashes on Android Chrome beta (32.0.1700.58)

michelle commented 10 years ago

@ericz can you try to reproduce on Android?

@demobo-com do you mean that the page itself crashes before you try to initiate any connections?

demobo-com commented 10 years ago

It crashes whenever video chat is connected.

ericz commented 10 years ago

@demobo-com is this Android to Android video chat or Android to Chrome? or both?

ericz commented 10 years ago

@demobo-com I tested it Chrome 32 desktop Chrome 32.0.1700.58 beta on Android, and also on Chrome 31 stable on Android.

Everything works great on Chrome 31 for Android.

In Chrome 32 for Android, upon video connection, everything freezes for about 30 seconds on my phone. During this time the Android 'Chrome is not responding" message shows up. If you click wait, then eventually connection will be complete and work like normal. (it does not crash for me, though maybe it would on other phones)

This is obviously bad behavior but I suspect the problem is with Chrome Beta's implementation, they sometimes will have issues before hitting stable such as this.

Have you experienced things working smoothly on a different webrtc example?

michelle commented 10 years ago

http://i.imgur.com/aLTpApz.jpg

demobo-com commented 10 years ago

Same problem on apprtc.appspot.com. It might be Chrome beta's problem. Thanks for your time. BTW, is peerjs server down today? Demos are not working for me since late last night.

michelle commented 10 years ago

Hm, seems to be fine for me (I'm able to get an ID on the chat demo)

Michelle

On Wed, Jan 8, 2014 at 10:10 AM, Jeff Lin notifications@github.com wrote:

Same problem on apprtc.appspot.com. It might be Chrome beta's problem. Thanks for your time. BTW, is peerjs server down today? Demos are not working for me since late last night.

— Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/137#issuecomment-31861249 .

demobo-com commented 10 years ago

http://cdn.peerjs.com/demo/chat.html Connection status: ERROR Error retrieving ID ERROR Aborting. Error: Could not get an ID from the server ERROR Error retrieving ID [object XMLHttpRequestProgressEvent] ERROR Aborting. Error: Could not get an ID from the server

console Failed to load resource http://0.peerjs.com:9000/lwjd5qra8257b9/id?ts=13892112930130.17142549180425704

michelle commented 10 years ago

hum. seems to be on and off. will poke.

Michelle

On Wed, Jan 8, 2014 at 12:03 PM, Jeff Lin notifications@github.com wrote:

http://cdn.peerjs.com/demo/chat.html Connection status: ERROR Error retrieving ID ERROR Aborting. Error: Could not get an ID from the server ERROR Error retrieving ID [object XMLHttpRequestProgressEvent] ERROR Aborting. Error: Could not get an ID from the server

console Failed to load resource http://0.peerjs.com:9000/lwjd5qra8257b9/id?ts=13892112930130.17142549180425704

— Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/137#issuecomment-31872333 .

demobo-com commented 10 years ago

In some networks, videochat example works but chat.html example doesn't work. Could this be caused by the "behind symmetric NATs" issue?

michelle commented 10 years ago

Notice any patterns? Are you using different devices?

Michelle

On Wed, Jan 8, 2014 at 2:39 PM, Jeff Lin notifications@github.com wrote:

In some networks, videochat example works but chat.html example doesn't work. Could this be caused by the "behind symmetric NATs" issue?

— Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/137#issuecomment-31883907 .

demobo-com commented 10 years ago

It seems like it is not related to network. It is device specific or chrome version.

Not working: Mac book pro using chrome 31.0.1650.63, another uses chrome 32 Mac book air using chrome 32.0.1700.72 beta

Working: Mac book pro using chrome 31.0.1650.63 Chrome book using chrome 31.0.1650.67

evan0322 commented 10 years ago

If I may, I would like to add some comment on this. I highly doubt that it is network and Chome version related. I got the same error with ERROR Aborting. Error: Could not get an ID from the server with a bad network on a tablet. Then I switch to other network and it worked perfectly. But I use desktop chrome browser in the previous network it is also working. It is wired but I listed here just in case someone want to dig into it.