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

[email protected] commented on MESOS-84:
----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3783/
-----------------------------------------------------------

(Updated 2012-02-10 21:27:41.014694)


Review request for mesos and Benjamin Hindman.


Summary
-------

This fixes some memory leaks of utility classes found through valgrind:

- the Slave never frees its Framework or Executor objects (this probably only 
affects the tests);
- the Master does not free its TaskDescriptionVisitor objects properly because 
the superclass does not have a virtual destructor (this is likely a slow memory 
leak for a running Master);


This addresses bug MESOS-84.
    https://issues.apache.org/jira/browse/MESOS-84


Diffs
-----

  src/master/master.cpp fd9e6fd 
  src/slave/slave.cpp 9b33a5a 

Diff: https://reviews.apache.org/r/3783/diff


Testing
-------


Thanks,

Charles


                
> Memory leak in master and scheduler (by way of libmesos.so)
> -----------------------------------------------------------
>
>                 Key: MESOS-84
>                 URL: https://issues.apache.org/jira/browse/MESOS-84
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Benjamin Hindman
>
> A noticeable memory leak affecting master machines (which host scheduler and 
> master) has been detected. On one machine, the master was observed consuming 
> a large amount of memory:
> PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
>                                                                               
>                                                                               
>                                                          
> 37908 root      20   0 14.3g  13g 5788 S  2.7 59.3 426:24.17 mesos-master
> This appears to affect the scheduler as well, since one machine shows a large 
> reclaiming of memory coincident with a scheduler process restart.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to