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

udp/stream: use MaybeStackBuffers to manage buffer memory management #8626

Closed
wants to merge 3 commits into from

Commits on Sep 17, 2016

  1. udp: use MaybeStackBuffer on DoSend

    instead of creating own buffer, use MaybeStackBuffer on DoSend to take advantage of its destructor to free up memory, so buffer never leaks memory - even if code in DoSend throws.
    Paul Kiddie committed Sep 17, 2016
    Configuration menu
    Copy the full SHA
    a345322 View commit details
    Browse the repository at this point in the history
  2. stream: uses MaybeStackBuffer in Writev

    Use MaybeStackBuffer in Writev to take advantage of destructor on MaybeStackBuffer to clear itself up, rather than Writev managing resources itself.
    Paul Kiddie committed Sep 17, 2016
    Configuration menu
    Copy the full SHA
    97d7e75 View commit details
    Browse the repository at this point in the history
  3. udp/stream: keeps default buffer size of 16 when creating MaybeStackB…

    …uffer
    Paul Kiddie committed Sep 17, 2016
    Configuration menu
    Copy the full SHA
    535ebac View commit details
    Browse the repository at this point in the history