-
Bug
-
Resolution: Unresolved
-
Minor
-
docker image:jenkins/jenkins:2.479.1-lts-jdk17
JAVA_OPTS:-Dhudson.model.DownloadService.noSignatureCheck=true -Duser.timezone=Asia/Shanghai
plugin version: 2.0.68.va_d21a_12a_6476
I found that when Jenkins runs for about two weeks, the memory will be completely occupied (the default upper limit of memory is 1G). Through memory analysis, I found that this object occupies more than 882.42MB. In the CopyOnWriteArrayList property of the internal class ConfigurationData under java.util.logging.Logger, there are a large number of org.jenkinsci.plugins.sshsteps.util.CustomLogHandler objects. This class does not implement the close method, and it is suspected to be related to this.
[JENKINS-74831] CustomLogHandler memory leak
Attachment | New: 微信截图_20241111131729.png [ 63512 ] |
Environment |
Original:
docker image:jenkins/jenkins:2.479.1-lts-jdk17
JAVA_OPTS:-Dhudson.model.DownloadService.noSignatureCheck=true -Duser.timezone=Asia/Shanghai |
New:
docker image:jenkins/jenkins:2.479.1-lts-jdk17
JAVA_OPTS:-Dhudson.model.DownloadService.noSignatureCheck=true -Duser.timezone=Asia/Shanghai plugin version: 2.0.68.va_d21a_12a_6476 |
Summary | Original: CostomLogHanlder memory leak | New: CustomLogHandler memory leak |