Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Close peerconnection ice gatherer on close #2658

Closed
wants to merge 4 commits into from

Conversation

SimonVerkada
Copy link
Contributor

Description

Closes peerconnection's ice gatherer (ice Agent) on close.

Reference issue

Fixes #...

Copy link

codecov bot commented Feb 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (v3@462a717). Click here to learn what that means.

Additional details and impacted files
@@          Coverage Diff          @@
##             v3    #2658   +/-   ##
=====================================
  Coverage      ?   78.56%           
=====================================
  Files         ?       76           
  Lines         ?     8860           
  Branches      ?        0           
=====================================
  Hits          ?     6961           
  Misses        ?     1485           
  Partials      ?      414           
Flag Coverage Δ
go 78.56% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +2087 to +2089
if pc.iceGatherer != nil {
closeErrs = append(closeErrs, pc.iceGatherer.Close())
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The iceTransport closes it's own gatherer, but the peerconnection also maintains it's own separate iceGatherer. Should close this one too.

@Sean-Der
Copy link
Member

Sean-Der commented Feb 3, 2024

Thanks @SimonVerkada (and great to see you again!)

What are the symptoms of the issue? Does this cause a memory/thread leak? Are you able to reproduce it at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants