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

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

    XMLWordPrintable

Details

    • Blue Ocean 1.2-beta2, Blue Ocean - Candidates

    Description

      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... 

       

       

      Attachments

        Activity

          In my case - classic view

          slavik334 Viachaslau Kabak added a comment - In my case - classic view
          slavik334 Viachaslau Kabak added a comment - Opened a new bug for Core https://issues.jenkins-ci.org/browse/JENKINS-47009
          michaelneale Michael Neale added a comment -

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

          michaelneale 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

          pwhoriskey 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
          whimboo 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/#/

          whimboo 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/#/

          People

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

            Dates

              Created:
              Updated: