Closed Bug 1121920 Opened 10 years ago Closed 10 years ago

[Dialer][CallScreen] JavaScript Error: "InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable"

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

x86
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gtorodelvalle, Assigned: gtorodelvalle)

References

Details

Attachments

(1 file, 1 obsolete file)

STR 1. Place an outgoing call and accept the call on the other end. 2. Place an incoming call. 3. Answer the incoming call. The previous call is now held and the incoming (call waiting) call is now connected. 4. Merge the calls in a conference. 5. End the conference call. OBSERVED: Although everything seems to be working fine, the following error is shown in the console: [JavaScript Error: "InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable" {file: "app://callscreen.gaiamobile.org/js/calls_handler.js" line: 241}] EXPECTED: No error should be shown in the console.
Assignee: nobody → gtorodelvalle
Bizarre, I've seen this happen when trying to use an IndexedDB transaction after it has completed. I think that it's thrown by native objects coming from Gecko that have exhausted their purpose but are still referenced by JS code. Considering where it's happening I wonder if we use a TelephonyCall object for a call that has already ended and removed from Telephony.calls or something similar.
Attached file Pull request 27500 (obsolete) —
Once again the reason of this bug is the event notification flow notified by the RIL when a conference call is hung up. In this case, the callschanged event is notified when the remaining call state is 'disconnected'. We just have to control this case and avoid accessing this disconnected call as we were wrongly doing ;) The point is that I do not recall seeing this log message on the console and it should have been there for a long time so I really do not know if there has been any change regarding the event notification flow on the backend side :(
Attachment #8551338 - Flags: review?(gsvelto)
Comment on attachment 8551338 [details] [review] Pull request 27500 LGTM, thanks for investigating this, last time I tracked one of these errors it took a while :-/
Attachment #8551338 - Flags: review?(gsvelto) → review+
It seems like we forgot to land this after the r+, here it goes.
Status: NEW → ASSIGNED
Keywords: checkin-needed
Keywords: checkin-needed
http://docs.taskcluster.net/tools/task-graph-inspector/#XBgFJTZjSACPXcgL9hosqg The pull request failed to pass integration tests. It could not be landed, please try again.
Keywords: checkin-needed
http://docs.taskcluster.net/tools/task-graph-inspector/#auy48SRUSl-2Kb9Zg5MdxA The pull request failed to pass integration tests. It could not be landed, please try again.
Comment on attachment 8613487 [details] [review] [gaia] gabrielesvelto:bug-1121920 > mozilla-b2g:master Somehow I cannot land the other PR, maybe due to its age, let's try again with this one.
Attachment #8613487 - Flags: review+
Attachment #8551338 - Attachment is obsolete: true
OK, let's see if this works.
Keywords: checkin-needed
Keywords: checkin-needed
http://docs.taskcluster.net/tools/task-graph-inspector/#HH_mkiMuSuuLJ0JnHZIshg The pull request failed to pass integration tests. It could not be landed, please try again.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: