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

Memory leak in Jenkins stage view

XMLWordPrintable

    • Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2

      Leaving a tab open with the stage view plugin active leaks memory with about 200MB every 10 minutes. Closing the tab and forcing a GC under 'about:memory' seems to recover the memory.

        1. jenkins-pipeline.diff
          1 kB
        2. stage-view-memory-leak.PNG
          stage-view-memory-leak.PNG
          93 kB

          [JENKINS-41558] Memory leak in Jenkins stage view

          Robin Björklin created issue -

          Robin Björklin added a comment -

          Added reference to possibly related issue.

          Robin Björklin added a comment - Added reference to possibly related issue.
          Robin Björklin made changes -
          Link New: This issue is related to JENKINS-34210 [ JENKINS-34210 ]

          Joachim Herb added a comment -

          I see exactly the same behavior (with the 32bit Windows version of Firefox (release 51.x and beta 52.x)). The "fix" at the moment is to use 64bit version.

          Joachim Herb added a comment - I see exactly the same behavior (with the 32bit Windows version of Firefox (release 51.x and beta 52.x)). The "fix" at the moment is to use 64bit version.

          Robin Björklin added a comment - - edited

          I'm running 64-bit Firefox version 51.0.1 under Linux if it makes any difference.

          UPDATE: I tried leaving a tab open in Chrome 56.0.2924.76 (64-bit), and it crashes after consuming more and more memory for awhile.

          Robin Björklin added a comment - - edited I'm running 64-bit Firefox version 51.0.1 under Linux if it makes any difference. UPDATE: I tried leaving a tab open in Chrome 56.0.2924.76 (64-bit), and it crashes after consuming more and more memory for awhile.
          Richard Kettelerij made changes -
          Attachment New: stage-view-memory-leak.PNG [ 35828 ]

          Richard Kettelerij added a comment -

          We're also experiencing this issue: We have a Windows 7 PC that continuously displays the Jenkins Stage View, it serves as a wallboard/information radiator. This PC is running Chrome (64 bits) and over time the stage view tab becomes slower and slower until it finally crashes. At that point the Chrome tab has accumulated about 1.5 - 2 GB of memory. When the stage view is open and you look in the Windows task manager you'll see the memory increasing every few seconds.

          Richard Kettelerij added a comment - We're also experiencing this issue: We have a Windows 7 PC that continuously displays the Jenkins Stage View, it serves as a wallboard/information radiator. This PC is running Chrome (64 bits) and over time the stage view tab becomes slower and slower until it finally crashes. At that point the Chrome tab has accumulated about 1.5 - 2 GB of memory. When the stage view is open and you look in the Windows task manager you'll see the memory increasing every few seconds.

          Richard Kettelerij added a comment -

          Our workaround: refresh the Chrome tab every few minutes using the SuperAutoRefresh plugin/extension to keep the memory from increasing above +/- 100mb.

          Richard Kettelerij added a comment - Our workaround: refresh the Chrome tab every few minutes using the SuperAutoRefresh plugin/extension to keep the memory from increasing above +/- 100mb.
          Richard Kettelerij made changes -
          Environment Original: Firefox (other browsers untested) New: Firefox (other browsers untested)
          Chrome 64bits on Windows

          Kevin Grandemange added a comment -

          To add to what was said:

          This happens with all major navigators: we have computers with Internet Explorer, Firefox and Chrome/Chromium in 32 / 64 bits accessing the stage view and the result is the same: an extremely fast leak that will keep eating memory until the machine isn't responsive anymore. This makes it impossible to keep an eye on the stage view at all time.

          So we use the same workaround than Richard Kettelerij but this makes the stage view essentially useless as you might be interrupted by a refresh while inspecting the pipeline

          Kevin Grandemange added a comment - To add to what was said: This happens with all major navigators: we have computers with Internet Explorer, Firefox and Chrome/Chromium in 32 / 64 bits accessing the stage view and the result is the same: an extremely fast leak that will keep eating memory until the machine isn't responsive anymore. This makes it impossible to keep an eye on the stage view at all time. So we use the same workaround than Richard Kettelerij but this makes the stage view essentially useless as you might be interrupted by a refresh while inspecting the pipeline

            Unassigned Unassigned
            rbjorklin Robin Björklin
            Votes:
            40 Vote for this issue
            Watchers:
            52 Start watching this issue

              Created:
              Updated: