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

Revert PR #1156 "Make DTLS fragment stay within MTU size range" because it causes a memory leak #1342

Merged
merged 4 commits into from
Feb 21, 2024

Commits on Feb 21, 2024

  1. Revert PR #1156 "Make DTLS fragment stay within MTU size range" becau…

    …se it causes a memory leak
    
    - Fixes #1340
    - Reopents #1100
    
    ### Details
    
    As perfectly documented in issue #1340, there is a leak due to the usage of `BIO_set_callback_ex()` whose fix is unclear and, anyway, I'm pretty sure that the usage of that OpenSSL utility makes the performance worse.
    
    As a workaround for issue #1100 (which now must be reopened), in order to avoid "DTLS fragment exceeds MTU size if the certificate is large", users should not pass a big DTLS certificate to mediasoup.
    ibc committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    f4e725f View commit details
    Browse the repository at this point in the history
  2. Update CHANGELOG

    ibc committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    6e31bf6 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    8d46a5f View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    cde9e7d View commit details
    Browse the repository at this point in the history