I don't know if this is Loop or the devtools at the moment. If I set a breakpoint in the Browser toolbox (not the web debugger), for a Loop conversation window whilst there is an ongoing WebRTC call, the call aborts straight away.

I've been seeing this for a while, but hadn't gotten around to filing a bug. My guess is that this is related to the fact that browser toolbox runs out-of-process. It's not at all obvious to me why this would happen, but adding a few folks to the CC who might care to hazard a guess...

(In reply to Dan Mosedale (:dmose) - not reading bugmail; needinfo? for response from comment #1) > I've been seeing this for a while, but hadn't gotten around to filing a bug. > My guess is that this is related to the fact that browser toolbox runs > out-of-process. It's not at all obvious to me why this would happen, but > adding a few folks to the CC who might care to hazard a guess... Just hazarding a guess here,

moving to tech-debt so it can be triaged against other tech-debt bugs.

I took a brief look at this just now as I was hitting it again today whilst trying to debug some tab sharing stuff. Interesting observations: - This doesn't happen if I use the web console - It doesn't seem to happen on apprtc - I turned on debugging and saw some information about the peerconnection being closed coming out of the sdk (unfortunately the browser then crashed :-( ) So I think this is either Loop related, or specific to something that we're doing in the webrtc land. Next steps might be to try this on other opentok based sites and other places like talky.io.

Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.