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

File system SCM uses more memory than expected with Jenkins 2.405 - 2.425

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core, filesystem_scm-plugin
    • 2.426, 2.414.3

      See my comments below, this issue started in 2.405

      (Same behavior happens whether running on same node as the master or not)

      I have a test job that triggers itself (also I set quiet period to 0), the job uses SCM to run the example Hello World pipeline

      After a few minutes, this is the result of http://localhost:8080/monitoring?part=heaphisto

      If I downgrade to 2.404.3 and try the same thing again....

        1. 2-405-after.png
          2-405-after.png
          208 kB
        2. 2-405-before.png
          2-405-before.png
          224 kB
        3. 2-404-after.png
          2-404-after.png
          208 kB
        4. 2-404-before.png
          2-404-before.png
          228 kB
        5. a-JENKINS-72067-git.tgz
          4 kB
        6. a-run-jenkins.sh
          0.8 kB
        7. a-plugins.txt
          2 kB
        8. 02-after-800-test-runs.png
          02-after-800-test-runs.png
          64 kB
        9. 01-before-test-run.png
          01-before-test-run.png
          77 kB
        10. JENKINS-72067-git.tgz
          2 kB
        11. run-jenkins.sh
          0.8 kB
        12. plugins.txt
          2 kB
        13. image-2023-09-25-08-42-47-692.png
          image-2023-09-25-08-42-47-692.png
          73 kB
        14. image-2023-09-24-11-28-08-440.png
          image-2023-09-24-11-28-08-440.png
          105 kB
        15. image-2023-09-24-10-46-06-168.png
          image-2023-09-24-10-46-06-168.png
          99 kB

          [JENKINS-72067] File system SCM uses more memory than expected with Jenkins 2.405 - 2.425

          Alex created issue -
          Alex made changes -
          Labels New: leak regression
          Alex made changes -
          Attachment Original: image-2023-09-24-10-40-22-371.png [ 61180 ]
          Alex made changes -
          Summary Original: Memory Leak in 2.414.2 New: Memory Leak in Jenkins LTS 2.414.1 and 2.414.2
          Alex made changes -
          Summary Original: Memory Leak in Jenkins LTS 2.414.1 and 2.414.2 New: Memory Leak in Jenkins 2.414.1 and 2.414.2
          Alex made changes -
          Environment Original: Jenkins: 2.414.2
          OS: Linux - 5.15.130-20444-g44e580fbe72b
          Java: 11.0.19 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
          ---
          antisamy-markup-formatter:162.v0e6ec0fcfcf6
          apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
          bouncycastle-api:2.29
          branch-api:2.1128.v717130d4f816
          caffeine-api:3.1.8-133.v17b_1ff2e0599
          cloudbees-folder:6.848.ve3b_fd7839a_81
          command-launcher:107.v773860566e2e
          commons-lang3-api:3.13.0-62.v7d18e55f51e2
          credentials:1271.v54b_1c2c6388a_
          credentials-binding:636.v55f1275c7b_27
          display-url-api:2.3.9
          durable-task:523.va_a_22cf15d5e0
          filesystem_scm:2.1
          git-client:4.5.0
          instance-identity:173.va_37c494ec4e5
          ionicons-api:56.v1b_1c8c49374e
          jackson2-api:2.15.2-350.v0c2f3f8fc595
          jakarta-activation-api:2.0.1-3
          jakarta-mail-api:2.0.1-3
          javax-activation-api:1.2.0-6
          javax-mail-api:1.6.2-9
          jaxb:2.3.8-1
          jdk-tool:73.vddf737284550
          mailer:463.vedf8358e006b_
          mina-sshd-api-common:2.10.0-69.v28e3e36d18eb_
          mina-sshd-api-core:2.10.0-69.v28e3e36d18eb_
          monitoring:1.95.0
          pipeline-build-step:505.v5f0844d8d126
          pipeline-groovy-lib:689.veec561a_dee13
          pipeline-input-step:477.v339683a_8d55e
          pipeline-milestone-step:111.v449306f708b_7
          pipeline-model-api:2.2144.v077a_d1928a_40
          pipeline-model-definition:2.2144.v077a_d1928a_40
          pipeline-model-extensions:2.2144.v077a_d1928a_40
          pipeline-stage-step:305.ve96d0205c1c6
          pipeline-stage-tags-metadata:2.2144.v077a_d1928a_40
          plain-credentials:143.v1b_df8b_d3b_e48
          scm-api:676.v886669a_199a_a_
          script-security:1275.v23895f409fb_d
          snakeyaml-api:2.2-111.vc6598e30cc65
          ssh-credentials:308.ve4497b_ccd8f4
          sshd:3.312.v1c601b_c83b_0e
          structs:325.vcb_307d2a_2782
          timestamper:1.26
          trilead-api:2.84.v72119de229b_7
          variant:60.v7290fc0eb_b_cd
          workflow-aggregator:596.v8c21c963d92d
          workflow-api:1281.vca_5fddb_3fceb_
          workflow-basic-steps:1042.ve7b_140c4a_e0c
          workflow-cps:3791.va_c0338ea_b_59c
          workflow-durable-task-step:1289.v4d3e7b_01546b_
          workflow-job:1326.ve643e00e9220
          workflow-multibranch:756.v891d88f2cd46
          workflow-scm-step:415.v434365564324
          workflow-step-api:639.v6eca_cd8c04a_a_
          workflow-support:865.v43e78cc44e0d
          New: Jenkins: 2.414.2
          OS: Linux - 5.15.130-20444-g44e580fbe72b
          Java: 11.0.19 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
          ---
          apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
          bouncycastle-api:2.29
          branch-api:2.1128.v717130d4f816
          caffeine-api:3.1.8-133.v17b_1ff2e0599
          cloudbees-folder:6.848.ve3b_fd7839a_81
          command-launcher:107.v773860566e2e
          credentials:1271.v54b_1c2c6388a_
          credentials-binding:636.v55f1275c7b_27
          display-url-api:2.3.9
          durable-task:523.va_a_22cf15d5e0
          filesystem_scm:2.1
          git-client:4.5.0
          instance-identity:173.va_37c494ec4e5
          ionicons-api:56.v1b_1c8c49374e
          jackson2-api:2.15.2-350.v0c2f3f8fc595
          jakarta-activation-api:2.0.1-3
          jakarta-mail-api:2.0.1-3
          javax-activation-api:1.2.0-6
          javax-mail-api:1.6.2-9
          jaxb:2.3.8-1
          jdk-tool:73.vddf737284550
          mailer:463.vedf8358e006b_
          mina-sshd-api-common:2.10.0-69.v28e3e36d18eb_
          mina-sshd-api-core:2.10.0-69.v28e3e36d18eb_
          monitoring:1.95.0
          pipeline-build-step:505.v5f0844d8d126
          pipeline-groovy-lib:689.veec561a_dee13
          pipeline-input-step:477.v339683a_8d55e
          pipeline-milestone-step:111.v449306f708b_7
          pipeline-model-api:2.2144.v077a_d1928a_40
          pipeline-model-definition:2.2144.v077a_d1928a_40
          pipeline-model-extensions:2.2144.v077a_d1928a_40
          pipeline-stage-step:305.ve96d0205c1c6
          pipeline-stage-tags-metadata:2.2144.v077a_d1928a_40
          plain-credentials:143.v1b_df8b_d3b_e48
          scm-api:676.v886669a_199a_a_
          script-security:1275.v23895f409fb_d
          snakeyaml-api:2.2-111.vc6598e30cc65
          ssh-credentials:308.ve4497b_ccd8f4
          sshd:3.312.v1c601b_c83b_0e
          structs:325.vcb_307d2a_2782
          trilead-api:2.84.v72119de229b_7
          variant:60.v7290fc0eb_b_cd
          workflow-aggregator:596.v8c21c963d92d
          workflow-api:1281.vca_5fddb_3fceb_
          workflow-basic-steps:1042.ve7b_140c4a_e0c
          workflow-cps:3791.va_c0338ea_b_59c
          workflow-durable-task-step:1289.v4d3e7b_01546b_
          workflow-job:1326.ve643e00e9220
          workflow-multibranch:756.v891d88f2cd46
          workflow-scm-step:415.v434365564324
          workflow-step-api:639.v6eca_cd8c04a_a_
          workflow-support:865.v43e78cc44e0d
          Alex made changes -
          Attachment New: image-2023-09-24-11-28-08-440.png [ 61181 ]
          Description Original: (Same behavior happens whether running on same node as the master or not)

          I have a test job that triggers itself (also I set quiet period to 0), the job uses SCM to run the example Hello World pipeline

          After a few minutes, this is the result of http://localhost:8080/monitoring?part=heaphisto

          !image-2023-09-24-10-51-40-981.png!

          If I downgrade to 2.404.3 and try the same thing again....

          !image-2023-09-24-10-46-06-168.png!
          New: (Same behavior happens whether running on same node as the master or not)

          I have a test job that triggers itself (also I set quiet period to 0), the job uses SCM to run the example Hello World pipeline

          After a few minutes, this is the result of [http://localhost:8080/monitoring?part=heaphisto]

          !image-2023-09-24-11-28-08-440.png!

          If I downgrade to 2.404.3 and try the same thing again....

          !image-2023-09-24-10-46-06-168.png!
          Alex made changes -
          Attachment Original: image-2023-09-24-10-51-40-981.png [ 61178 ]
          Alex made changes -
          Summary Original: Memory Leak in Jenkins 2.414.1 and 2.414.2 New: Memory Leak from Jenkins 2.405 and up
          Alex made changes -
          Description Original: (Same behavior happens whether running on same node as the master or not)

          I have a test job that triggers itself (also I set quiet period to 0), the job uses SCM to run the example Hello World pipeline

          After a few minutes, this is the result of [http://localhost:8080/monitoring?part=heaphisto]

          !image-2023-09-24-11-28-08-440.png!

          If I downgrade to 2.404.3 and try the same thing again....

          !image-2023-09-24-10-46-06-168.png!
          New: *See my comments below, this issue started in 2.405*

          (Same behavior happens whether running on same node as the master or not)

          I have a test job that triggers itself (also I set quiet period to 0), the job uses SCM to run the example Hello World pipeline

          After a few minutes, this is the result of [http://localhost:8080/monitoring?part=heaphisto]

          !image-2023-09-24-11-28-08-440.png!

          If I downgrade to 2.404.3 and try the same thing again....

          !image-2023-09-24-10-46-06-168.png!
          Alex made changes -
          Comment [ [~markewaite] oops I just added that *Legacy SCM* needs to be selected for Retrieval method and *File System* needs to be selected for Source Code Management, I edited that comment above.

           

          Let me know if following that works for you or not ]

            markewaite Mark Waite
            alexsch01 Alex
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: