Skip to content
This repository has been archived by the owner on Oct 9, 2021. It is now read-only.

Deregister edge WebRTC session after publisher disconnected #8

Open
williamlsh opened this issue Apr 12, 2021 · 1 comment
Open

Deregister edge WebRTC session after publisher disconnected #8

williamlsh opened this issue Apr 12, 2021 · 1 comment

Comments

@williamlsh
Copy link
Collaborator

williamlsh commented Apr 12, 2021 •
edited
Loading

The increase of unhandled orphan TrackLocal will increase memory usage and incur memory leak. Must tidy these resource after frontend WebRTC disconnected.
williamlsh added a commit that referenced this issue Apr 12, 2021
@williamlsh
Tidy RTPSender after disconnecting(#8)
f755a14
@williamlsh williamlsh changed the title Handle disconnected PeerConnections and tracks in case of memory leak Handle disconnected TrackLocals in case of memory leak Apr 13, 2021
@williamlsh williamlsh changed the title Handle disconnected TrackLocals in case of memory leak Deregister edge WebRTC session after publisher disconnected Apr 13, 2021
williamlsh added a commit that referenced this issue Apr 13, 2021
@williamlsh
Deregister session after publisher disconnected(#8)
6d09a50
@williamlsh williamlsh reopened this Apr 15, 2021
@williamlsh
Copy link
Collaborator Author

Deregistering session on ICE close will undo normal session registration of the same device track source, because ICE close event has a lantency. When sesion re-registered, a late ICE close event de-registeres it causing frontend subscriber finding no exisitng session to connect.

williamlsh added a commit that referenced this issue Apr 15, 2021
@williamlsh
Remove deregister session(#8)
9581dd0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@williamlsh