[jira] [Commented] (MESOS-4060) Memory Leak in Default Mesos UI

["Orlando Hohmeier (JIRA)" <ji...@apache.org>]

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

Orlando Hohmeier commented on MESOS-4060:
-----------------------------------------

Related Marathon Issue: https://github.com/mesosphere/marathon/issues/2755

> Memory Leak in Default Mesos UI
> -------------------------------
>
>                 Key: MESOS-4060
>                 URL: https://issues.apache.org/jira/browse/MESOS-4060
>             Project: Mesos
>          Issue Type: Bug
>          Components: webui
>    Affects Versions: 0.25.0
>         Environment: All 
>            Reporter: John Omernik
>
> Basically, in using Firefox, I noticed that over time, my Firefox would get to become unusable when I had Marathon and Mesos WebUIs up and running.  At first, I thought it was a function of my home (Mac) computer and Firefox. But when I started a PoC for work, and my Windows install of Firefox had the same issues, I started doing more investigation. 
> First of all, both at home and at work, my Firefox is only dedicated to "cluster" related tasks. Thus, I don't have other tabs that are not Cluster UIs.  
> My typical setup is to have MapR UI, Mesos UI, Marathon UI, Chronos UI, Myriad UI, and Yarn UI all up and running.  
> After about 3-4 hours, my browser would get really slow, and non-responsive. I'd kill all and start again.  Rinse repeat.  
> So I did some analysis, and basically found a plugin for Firefox that shows on each tab the amount of memory being used. I found that both Marathon and Mesos UI were the culprits, and things got really bad after just 2-3 hours.  With those setup, on Windows, I have the following memory usage:
> MapR UI: 7.7mb
> Myriad UI: 9.8mb
> Yarn: 2.7 mb
> Chronos 10.2 mb
> Marathon: 163 mb
> Mesos UI: 463 mb
> Both Marathon and Mesos continually climb, slowly, up some, down a few, up some more, but obviously generally trending up.  I guess I wanted to toss it out here to see if it's something in my settings, or something that others are seeing.  It's a problem for me from a usability standpoint, and I am guessing that it's one of those things that while not a priority for a project, should be looked at. 



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