You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2016/07/13 18:01:20 UTC
[jira] [Updated] (MESOS-5144) Cleanup memory leaks in libprocess
finalize()
[ https://issues.apache.org/jira/browse/MESOS-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Wu updated MESOS-5144:
-----------------------------
Shepherd: Joseph Wu
Sprint: Mesosphere Sprint 39
Story Points: 2
These reviews were posted by Neil a while ago:
|| Review || Summary ||
| https://reviews.apache.org/r/45991/ | Leak in {{Route}} |
| https://reviews.apache.org/r/45995/ | Leak in {{initialize}} |
| https://reviews.apache.org/r/45996/ | Leak of {{gc}} |
| https://reviews.apache.org/r/45999/ | Leak in {{finalize}} |
| https://reviews.apache.org/r/46094/ | Leak in tests |
| https://reviews.apache.org/r/46146/ | More test leaks |
> Cleanup memory leaks in libprocess finalize()
> ---------------------------------------------
>
> Key: MESOS-5144
> URL: https://issues.apache.org/jira/browse/MESOS-5144
> Project: Mesos
> Issue Type: Task
> Components: libprocess
> Reporter: Neil Conway
> Assignee: Neil Conway
> Labels: mesosphere, tech-debt
> Attachments: libprocess_finalize_mem_leaks-1.patch
>
>
> libprocess's {{finalize}} function currently leaks memory for a few different reasons. Cleaning up the {{SocketManager}} will be somewhat involved (MESOS-3910), but the remaining memory leaks should be fairly easy to address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)