feross / feross/simple-peer

So many seemingly dangling peer connections, even if no peer is open

Open
#920 7 comments 2 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
7.8k
Forks
983
PR merge metrics
No merged PRs in 30d

Description

Right after launching my app, which is at this moment just inserted the simple-peer script by HTML script tag (no peer open), I'm observing three of such entries in webrtc-internals, from which one disappears after a minute:

image

After having held a couple of session, which are all terminated with peer.destroy() the number of those entries has increased dramatically. Only the complete termination of the browser page removes these entries.

Is this just a laziness of the WebRTC internal process, which keeps this statistics open, or am I doing something wrong?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.