Leaking RTCPeerConnections. Even after page refresh
<p>I have a pretty simple RTCPeerConnection app running. Uses Firebase for signaling. The RTCPeerConnections get established, and then I take the stream, and do the following with it:</p>

<pre><code>let streamURL = window.URL.createObjectURL(stream);
</code></pre>

<p>Then I take that <code>streamURL</code> and set the <code>video.src = streamURL</code>. That is how I get it to see the remote users' video. Then, when I am done with the connection (I want to end the conversation) I do the following:</p>

<pre><code>peerConnection.getLocalStreams().forEach(stream=&gt;{
    stream.getTracks().forEach(t=&gt;{
        t.stop();
        stream.removeTrack(t);
    });
});
peerConnection.close();
</code></pre>

<p>This ends the connection, including turns off the green light for my local webcam. This tells me that things have ended for the most part. </p>

<p>Then I check <a href="http://chrome://webrtc-internals" rel="nofollow">chrome://webrtc-internals</a> and the connection is still there. Even after I refresh, the connection is there. That seems odd. How can it still be there, even after a refresh? Please help. Am I not ending the RTCPeerConnection correctly? I thought this was the right way. I just can't figure out how the webrtc internals can still show it EVEN AFTER a page refresh. PLEASE HELP!</p>