Closed
Bug 1076066
Opened 11 years ago
Closed 10 years ago
Loop call disconnects a few seconds after connection established
Categories
(Core :: WebRTC, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
backlog | webrtc/webaudio+ |
People
(Reporter: billm, Unassigned)
Details
Attachments
(1 file)
512.52 KB,
text/html
|
Details |
This happened to me twice: once with e10s enabled and once with it disabled. I realize this isn't a very useful bug report. Is there anything I can do in the future to help explain the issue?
I'm also experiencing an issue where I can still see and hear the other party, but they can't see or hear me. Hitting reload solves the problem.
Comment 1•11 years ago
|
||
Bill -- Are you always the "link clicker" (the recipient of a URL) on the call when this happens? Do you see this when you generate the URL (and send it to another user)?
How reproducible is this?
Next time you see this: can you go to "about:webrtc", press "connection log", copy the contents of the page, and attach it to this bug?
Flags: needinfo?(wmccloskey)
Reporter | ||
Comment 2•11 years ago
|
||
In this case I was the link clicker. I haven't tried as the sender of the link.
Would it still be useful to attach my connection log now? There's an enormous amount of stuff there. I haven't restarted since the problem happened.
Flags: needinfo?(wmccloskey)
Comment 3•11 years ago
|
||
Yes, it's worth uploading. Do you happen to know how many calls you made since you saw the problem?
Comment 4•11 years ago
|
||
(In reply to Bill McCloskey (:billm) from comment #0)
> I'm also experiencing an issue where I can still see and hear the other
> party, but they can't see or hear me. Hitting reload solves the problem.
This sounds like a camera grant issue. Can you recall whether you granted access to the camera for these calls? It's very easy to accidentally click away from the prompt that asks for access, and not obvious that it's still waiting for you when you do so.
Reporter | ||
Comment 5•11 years ago
|
||
It may have been related to the camera privileges. I'm pretty sure I clicked the right button. It did seem to disconnect around that time.
The behavior I saw was that the screen went black again (could no longer see the other party) and was replaced with something asking me how the experience was.
Here's the about:webrtc data. It includes several calls. The last one was successful. Before that there were two calls that ended unexpectedly after about 5 minutes (this is the second problem I described). And before that there were two attempted calls that ended after about 2 seconds (this is the first problem I described). In all of these I was the link clicker.
Reporter | ||
Comment 6•11 years ago
|
||
To clarify, in the calls that ended after 5 minutes, I could see the other party but they couldn't see me. So I reloaded to start the call over again.
Comment 7•11 years ago
|
||
From the perspective of the other side of the call, Bill just froze (both audio and video) about 5 minutes into our call. He could apparently still see and hear my video though.
Comment 8•10 years ago
|
||
Bill - I believe this problem has been resolved for you. If so, can we close ot?
backlog: --- → webRTC+
Rank: 25
Flags: needinfo?(wmccloskey)
Priority: -- → P2
Reporter | ||
Comment 9•10 years ago
|
||
I guess so. I haven't used Loop in a while.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(wmccloskey)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•