I am not sure I have filed this under the right component.

We are seeing steady gradual increases in memory usage for our Jenkins (see attached graphs). It does not result in the OutOfMemoryError but usually results in Jenkins utilizing 100% of CPU (one core in our case).

Attached is a memory histogram report and the link include (see URL above) is to a heap dump generated using the Monitoring Plugin.

This happens consistently and our work around for now is to restart Jenkins each time it gets too bloated. If this doesn't get fixed, we will have to stop using Winstone and use Jetty - because there seems to be a connection between the servlet wrapper (winstone/jetty) and the leak - pretty sure we did not see this when using Jetty.