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

Fix memory leak on http binary send #126

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

flatline
Copy link

The internal http write buffer was allocating copies of data it never deleted.

By the time the std::vector destructor was getting called, the vector size was already 0
and any data pointers were invalid.

Extending std::vector here is questionable, but this should patch the memory leak
with minimal impact on the existing code.

All sent memory was being leaked during binary sends.

The old deletion scheme didn't work because the container size was already
0 by the time the destructor was hit and it was effectively a no-op.
firedaemon-cto pushed a commit to FireDaemon/pion that referenced this pull request Aug 27, 2020
…plunk#126)

* initial set of core changes for constexpr support (issue splunk#123)

* fixes for constexpr core support based on ci failures (issue splunk#123)

* drive by fix for gcc9.2 warning on polymorphic exception

* fixes for constexpr core support based on for cpp11 and cpp14 build variants (issue splunk#123)

* more fixes for constexpr core support  (issue splunk#123) - also fix for issue splunk#124

* next round of changes for constexpr core support (issue splunk#123)

* fix last msvc regression for constexpr core

* driveby fix to remove detail include

* 3rd round of changes for constexpr

* yet another msvc fix for cpp14

* minor doc fix for issue splunk#127 - tm_isddst -> tm_isdst

* minor doc fix for issue splunk#127 - tm_isddst -> tm_isdst

* push constexpr deep into the library including date, ptime (issue splunk#123)

* push constexpr deep into the library including date, ptime (issue splunk#123)

* fix latests regressions from constexpr changes in older gcc
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.

1 participant