fpm123 / sipml5

Automatically exported from code.google.com/p/sipml5
0 stars 0 forks source link

firefox nightly returns: [Exception... "Unexpected error" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" #123

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Initiate a call using Firefox nightly
2. Look in console log

What is the expected output? What do you see instead?

A successful call.

What version of the product are you using? On what operating system?

Firefox nightly (26.0a1 (2013-09-01)) on Linux
sipml5 code: r210

Please provide any additional information below.

Full error happens after mozRTCPeerConnection():

[Exception... "Unexpected error"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  
location: "JS frame :: https://live.mayfirst.org/mexcla/js/sipml5/SIPml-api.js 
:: tmedia_session_jsep01.prototype.__get_lo :: line 3"  data: no]
https://live.mayfirst.org/mexcla/js/sipml5/SIPml-api.js
Line 1

Original issue reported on code.google.com by jmcclell...@gmail.com on 1 Sep 2013 at 8:35

GoogleCodeExporter commented 8 years ago
Can we get an update on this? This is high priority since it is blocking usage 
on Firefox.  Also seeing this on windows too.

Original comment by oldblue...@gmail.com on 29 Oct 2013 at 1:44

GoogleCodeExporter commented 8 years ago
Hi
I'm also having this error with firefox when the call is terminated.
I'm attaching the console output.

Original comment by cybpe...@gmail.com on 29 Oct 2013 at 1:57

Attachments:

GoogleCodeExporter commented 8 years ago
It looks like the following change in Firefox is breaking SIPml5:

"Unexpose the removeStream function on the Peer Connection object temporarily"
https://bugzilla.mozilla.org/show_bug.cgi?id=844295

SIPml is calling removeStream when terminating a call, which results in an 
error.
In the SIPml5 source I replaced:

this.o_pc.removeStream(this.o_local_stream);

with:

if (SIPml.getNavigatorFriendlyName() !== "firefox") 
this.o_pc.removeStream(this.o_local_stream);

Hope this helps.

Original comment by hoffmann...@gmail.com on 4 Nov 2013 at 2:39

GoogleCodeExporter commented 8 years ago
Thanks a lot. In my case the error is gone when call is terminated.

Original comment by cybpe...@gmail.com on 5 Nov 2013 at 12:54

GoogleCodeExporter commented 8 years ago
We also removed the calls to removeStream() when working with Firefox, which 
allowed proper call termination.

Original comment by michelle...@gmail.com on 20 Dec 2013 at 3:56