[
https://issues.apache.org/jira/browse/MESOS-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427582#comment-15427582
]
ASF GitHub Bot commented on MESOS-6038:
---------------------------------------
Github user aaronjwood commented on the issue:
https://github.com/apache/mesos/pull/157
It looks like I was wrong about this, I had thought the copy constructor of
tuple was getting called when it wasn't the copy constructor at all. I did some
more testing with this and found that the original version behaves properly.
> Prevent leaking allocated memory for Promises
> ---------------------------------------------
>
> Key: MESOS-6038
> URL: https://issues.apache.org/jira/browse/MESOS-6038
> Project: Mesos
> Issue Type: Bug
> Components: c++ api, libprocess
> Reporter: Aaron Wood
> Priority: Minor
> Labels: github-import, patch
>
> I had found a few places where these Promise objects were leaking. Once the
> Future was returned there was no way to free the memory for the Promise
> object that had been allocated thus causing the leak.
> https://reviews.apache.org/r/51068/
> https://github.com/apache/mesos/pull/157
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
