You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/11/02 04:43:58 UTC

[jira] [Commented] (MESOS-6527) Memory leak in the libprocess request decoder.

    [ https://issues.apache.org/jira/browse/MESOS-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627701#comment-15627701 ] 

Anand Mazumdar commented on MESOS-6527:
---------------------------------------

{noformat}
commit 315b9cdad33ee3fe653df1698d4f21711b10c0e9
Author: Anand Mazumdar <an...@apache.org>
Date:   Tue Nov 1 21:32:55 2016 -0700

    Fixed memory leak in request/response decoders.

    The leak can happen in cases where a client disconnects while the
    request/response is in progress.

    Review: https://reviews.apache.org/r/53361/
{noformat}

> Memory leak in the libprocess request decoder.
> ----------------------------------------------
>
>                 Key: MESOS-6527
>                 URL: https://issues.apache.org/jira/browse/MESOS-6527
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: Anand Mazumdar
>            Assignee: Anand Mazumdar
>            Priority: Blocker
>              Labels: mesosphere
>
> The libprocess decoder can leak a {{Request}} object in cases when a client disconnects while the request is in progress. In such cases, the decoder's destructor won't delete the active {{Request}} object that it had allocated on the heap.
> https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/decoder.hpp#L271



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)