Closed hellojukay closed 1 year ago
The issue tracker for the jenkins.io documentation site is used to track issues with the Jenkins documentation.
Please use the Jenkins issue tracker for bug reports. Btw. with the Monitoring plugin that you have installed you should be able to do a heap dump and analyze that to see what class(es) are the main problem -- that might be helpful in deciding which plugin is causing this.
Jenkins will occupy very little memory when it is first started, but as time goes by, Jenkins will occupy more and more memory, especially the memory in the G1 Old Gen area will not be released, and it will become larger and larger (this process (is slow), even if no one uses Jenkins on weekends, its memory will increase
Jenkins and plugins
Problem with this page
https://community.jenkins.io/t/jenkins-memory-leak/10309
Expected behavior
Jenkins can release memory when it is idle. The space of G1 Old gen does not grow slowly all the time.
Actual behavior
Jenkins did not release part of the memory when it was idle. G1 Old Gen has been growing slowly and finally reached the Xmx limit.
Possible solution
A memory leak occurred in Jenkins Core or some specific plugin.