Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45094

Memory usage on dashboard, activity pages after browser is open a long time

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Blue Ocean 1.2-beta2, Blue Ocean - Candidates

      There have been occasional reports of high memory usage when keeping blue ocean open in a tab for many many hours. 

      It isn't clear what page yet, but it is worth investigating: 

       

      • Dashboard main page
      • Activity page for a given build

       

      Ideally in cases where there are running builds. What should be noted is if there is monotonically increasing memory usage for the tab. If there is - likely candidates are SSE events loading data into a store (something like mobx) which probably should be more of a buffer... 

       

       

          [JENKINS-45094] Memory usage on dashboard, activity pages after browser is open a long time

          Henrik Skupin added a comment -

          I reported a similar issue with Firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=751557 years ago. The problem might still happen for our Jenkins instance given that we are behind updating it, and might shut it down soon. But at the time when I tried to investigate we got less help, so I stopped the investigation.

          We never used the beforementioned plugin, but I had the feeling that things got worse when lots of jobs got added via the Jenkins API. This might be unrelated to what you see here, but I just wanted to give this information.

          Henrik Skupin added a comment - I reported a similar issue with Firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=751557 years ago. The problem might still happen for our Jenkins instance given that we are behind updating it, and might shut it down soon. But at the time when I tried to investigate we got less help, so I stopped the investigation. We never used the beforementioned plugin, but I had the feeling that things got worse when lots of jobs got added via the Jenkins API. This might be unrelated to what you see here, but I just wanted to give this information.

          Every day I have to restart FF cause of it takes 16Gb RAM. Viewing job pipeline stages in about 10 tabs. Memory usage the same in chrome.

          I can give you all needed info and data. Also you can get it from the ticket https://bugzilla.mozilla.org/show_bug.cgi?id=791695#c33

          Viachaslau Kabak added a comment - Every day I have to restart FF cause of it takes 16Gb RAM. Viewing job pipeline stages in about 10 tabs. Memory usage the same in chrome. I can give you all needed info and data. Also you can get it from the ticket https://bugzilla.mozilla.org/show_bug.cgi?id=791695#c33

          Michael Neale added a comment -

          whimboo slavik334 can you confirm this is with blue ocean or if it is the 'classic' stage view? (ie boxes?)

          Michael Neale added a comment - whimboo slavik334 can you confirm this is with blue ocean or if it is the 'classic' stage view? (ie boxes?)

          Henrik Skupin added a comment -

          At least in my case it's the classic view. We never used Blue Ocean. Also our CI system is still on Jenkins 1.580.3, so it may not even be available. Please note that I cannot help with running a recent version of Jenkins given that it would require lots of work, and as I said above we are shutting down the service soon. But all the code is available here: https://github.com/mozilla/mozmill-ci. If all this should go into a different issue please note and I can file one.

          Henrik Skupin added a comment - At least in my case it's the classic view. We never used Blue Ocean. Also our CI system is still on Jenkins 1.580.3, so it may not even be available. Please note that I cannot help with running a recent version of Jenkins given that it would require lots of work, and as I said above we are shutting down the service soon. But all the code is available here: https://github.com/mozilla/mozmill-ci. If all this should go into a different issue please note and I can file one.

          Michael Neale added a comment -

          whimboo yes probably not this ticket in that case - you can open it against the core component ideally. 

          Michael Neale added a comment - whimboo yes probably not this ticket in that case - you can open it against the core component ideally. 

          In my case - classic view

          Viachaslau Kabak added a comment - In my case - classic view

          Viachaslau Kabak added a comment - Opened a new bug for Core https://issues.jenkins-ci.org/browse/JENKINS-47009

          Michael Neale added a comment -

          ok so it seems all the new information is in the classic stage view... 

          Michael Neale added a comment - ok so it seems all the new information is in the classic stage view... 

          Just adding a data point in case it helps: 

           

          On linux/Firefox, I can see a running build page grow from ~40Mb to over 2Gb over the course of an hour or so.  the majority of that space, ~1.6Gb is listed under dom/orphan-nodes.  

          Jenkins 2.190.1

          Firefox 60.9.0esr

          Phillip Whoriskey added a comment - Just adding a data point in case it helps:    On linux/Firefox, I can see a running build page grow from ~40Mb to over 2Gb over the course of an hour or so.  the majority of that space, ~1.6Gb is listed under dom/orphan-nodes.   Jenkins 2.190.1 Firefox 60.9.0esr

          Henrik Skupin added a comment -

          pwhoriskey, if you could install a recent Nightly build of Firefox 72.0 and install the profiler addon from https://profiler.firefox.com/, you could create a profile which might help to figure out where the leak actually is happening. See the documentation in how to create and upload a profile: https://profiler.firefox.com/docs/#/

          Henrik Skupin added a comment - pwhoriskey , if you could install a recent Nightly build of Firefox 72.0 and install the profiler addon from https://profiler.firefox.com/, you could create a profile which might help to figure out where the leak actually is happening. See the documentation in how to create and upload a profile: https://profiler.firefox.com/docs/#/

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: