[JIRA] Created: (JENKINS-10912) Memory leak (?) in dashboard

Memory leak (?) in dashboard
----------------------------

                 Key: JENKINS-10912
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
             Project: Jenkins
          Issue Type: Bug
          Components: dashboard-view
    Affects Versions: current
         Environment: windows jenkins server
windows client
chrome browser
autorefresh is enabled
            Reporter: david abadir
            Assignee: Peter Hayes
            Priority: Minor


leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157984#comment-157984 ]

Nicolas Calderon commented on JENKINS-10912:
--------------------------------------------

I've noticed memory inflation of 1GB overnight with our Jenkins, and the issue seems to be present on the demo jenkins (http://ci.jenkins-ci.org/). I didn't leave it open for that long, but it did increase by 10MB over 10-15 minutes.

I use Chrome 17 (beta) and tried to see where all that memory was going with dev tools. I tried taking a heap snapshot of my 1GB tab but it crashed it. I tried again after just 10MB of "leak" but couldn't notice much difference in components size. I did notice that memory fluctuates whenever there is network traffic, which occurs when there are ajax requests (ajaxBuildQueue, ajaxExecutors). Those are triggered whether auto refresh is enabled or not (in my case, auto refresh were disabled).
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: dashboard-view
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Assignee: Peter Hayes
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162217#comment-162217 ]

Laura Neff commented on JENKINS-10912:
--------------------------------------

I've noticed this on Jenkins 1.460, running on Windows, I'm using FireFox.  My Jenkins instance seems to be constantly growing in size, I hoped upgrading to 1.460 from approx. 1.420 would help, but doesn't seem to be doing so.  This morning I notice that with 1.460, and autorefresh off, just navigating from one Jenkins page to another causes memory usage to increase several K, and space never seems to be recovered.  Our Jenkins instance is quiet this morning, no jobs running.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: dashboard-view
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Assignee: Peter Hayes
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Hayes updated JENKINS-10912:
----------------------------------

       Assignee:     (was: Peter Hayes)
    Component/s: core
                     (was: dashboard-view)

I think this should be filed against core, not the dashboard view plugin.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162288#comment-162288 ]

Anoop Karollil commented on JENKINS-10912:
------------------------------------------

We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162288#comment-162288 ]

Anoop Karollil edited comment on JENKINS-10912 at 5/1/12 9:21 PM:
------------------------------------------------------------------

We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related and the number of sessions dropped to 4 a bit after. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1
               
      was (Author: akarollil):
    We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1
                 

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162288#comment-162288 ]

Anoop Karollil edited comment on JENKINS-10912 at 5/1/12 9:31 PM:
------------------------------------------------------------------

We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related and the number of sessions dropped to 4 a bit after. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1


We recently switched from using Jetty as a container for Jenkins to Winstone. But again, I don't know if that is relevant.
               
      was (Author: akarollil):
    We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related and the number of sessions dropped to 4 a bit after. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1
                 

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162288#comment-162288 ]

Anoop Karollil edited comment on JENKINS-10912 at 5/1/12 9:33 PM:
------------------------------------------------------------------

We are seeing this problem too (on v1.461). Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related and the number of sessions dropped to 4 a bit after. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1


We recently switched from using Jetty as a container for Jenkins to Winstone. But again, I don't know if that is relevant.
               
      was (Author: akarollil):
    We are seeing this problem too. Over time Jenkins uses about 700MB for about 10 jobs. The 'Monitoring' plugin (quite useful by the way) lets you do a garbage collection but that cleared up only 30MB. The histogram shows about 150MB usage over the past week and then a quick ramp yesterday from 150MB to 700MB. There was a jump in number of sessions from 3 to 9 around the time just before the ramping in memory usage happened. I am not sure if its related and the number of sessions dropped to 4 a bit after. CPU usage is also quite high right now, mostly tying down one CPU core.

Memory histogram shows this:

Class Size (Kb) % size Instances % instances
byte[] 132,623 17 179,202 1
char[] 125,861 16 1,630,859 9
java.util.HashMap$Entry 65,111 8 2,778,092 16
java.util.HashMap$Entry[] 51,225 6 700,897 4
java.lang.String 43,672 5 1,863,370 11
java.lang.Object[] 30,612 4 453,476 2
java.util.WeakHashMap$Entry 28,414 3 727,415 4
java.util.HashMap 27,029 3 691,947 4
java.util.WeakHashMap$Entry[] 19,986 2 194,526 1
java.util.Hashtable$Entry[] 17,852 2 311,216 1
java.util.Hashtable 11,176 1 286,110 1
java.util.WeakHashMap 9,118 1 194,526 1
org.apache.commons.jelly.JellyContext 8,378 1 214,498 1 storage/sw/hudson/war/WEB-INF/lib/commons-jelly-1.1-jenkins-20110627.jar
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1 8,090 1 115,058 0 storage/sw/hudson/war/WEB-INF/lib/stapler-jelly-1.187.jar
java.lang.String[] 7,711 1 174,016 1
java.util.ArrayList 7,655 1 326,640 1


We recently switched from using Jetty as a container for Jenkins to Winstone. But again, I don't know if that is relevant.
                 

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162620#comment-162620 ]

Anoop Karollil commented on JENKINS-10912:
------------------------------------------

This seems to happen only when using Chrome, possibly having auto-refresh enabled and leaving the tab open all the time.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans-Juergen Hafner updated JENKINS-10912:
------------------------------------------

    Attachment: OoM.jpg
   

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>         Attachments: OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162640#comment-162640 ]

Hans-Juergen Hafner commented on JENKINS-10912:
-----------------------------------------------

We have also Problems with Firefox on Linux and Windows 7 and Internet Explorer on Windows 7.
After some time IE shows following error:
!OoM.jpg!
In this case, autorefresh was disabled.
We observed this memory leak using Jenkins 1.457 and 1.459. Currently we are using 1.454. This version seems to have no problem with memory leaks in browser.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>            Priority: Minor
>         Attachments: OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans-Juergen Hafner updated JENKINS-10912:
------------------------------------------

    Priority: Major  (was: Minor)

I changed Priority to Major, because our developers are not willing to use a version with this issue.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>         Attachments: OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162656#comment-162656 ]

Anoop Karollil commented on JENKINS-10912:
------------------------------------------

Firefox 12.0 on Ubuntu 12.04 with Jenkins 1.4.63 with auto-refresh and Jenkins tab open all the time doesn't result in memory leak for us.
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>         Attachments: OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans-Juergen Hafner updated JENKINS-10912:
------------------------------------------

    Attachment: mem_1.460.jpg
                mem_1.457.jpg

Memory consumption Firefox 12.0 (Red Hat Enterprise Linux Server release 6.0)
               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>         Attachments: mem_1.457.jpg, mem_1.460.jpg, OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162737#comment-162737 ]

Hans-Juergen Hafner commented on JENKINS-10912:
-----------------------------------------------

I seems the problemm disappeared.
I made a memory consumption log of Firefox 12 with top in batch mode.
The following diagram shows increase of memory with Jenkins 1.457:

               

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>         Attachments: mem_1.457.jpg, mem_1.460.jpg, OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162737#comment-162737 ]

Hans-Juergen Hafner edited comment on JENKINS-10912 at 5/14/12 3:45 PM:
------------------------------------------------------------------------

It seems the problem disappeared.
I made a memory consumption log of Firefox 12 on Red Hat Enterprise Linux 6.0 with top in batch mode. I opened dashboard and let Jenkins alone.
The following diagram shows increase of memory with Jenkins 1.457:
!mem_1.457.jpg|width=30%!
and here constant memory with Jenkins 1.460:
!mem_1.460.jpg|width=30%!
               
      was (Author: hjhafner):
    I seems the problemm disappeared.
I made a memory consumption log of Firefox 12 with top in batch mode.
The following diagram shows increase of memory with Jenkins 1.457:

                 

> Memory leak (?) in dashboard
> ----------------------------
>
>                 Key: JENKINS-10912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10912
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: windows jenkins server
> windows client
> chrome browser
> autorefresh is enabled
>            Reporter: david abadir
>         Attachments: mem_1.457.jpg, mem_1.460.jpg, OoM.jpg
>
>
> leaving the dashboard webpage open (with autorefresh) will accumulate lots of memory.  I left it open over the weekend and it was using over 700 MB of ram!  you can watch the memory consumption increase ~3-10 MB every time it refreshes (manually or automatically).  Sometimes it will decrease to the pre-refreshed amount, but it will always increase over time (instantaneous readings may/may not prove true, but long term averages will).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Jonas Olsson commented on JENKINS-10912

Memory leak (?) in dashboard

We still experience the problem in Jenkins 1.459. Leave the dashboard open during the night and memory will be eaten. Both Firefox and Chrome seems to be affected. OS is Ubuntu.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Trinh commented on JENKINS-10912

Memory leak (?) in dashboard

I'm still getting this error on 1.472. The problem occurred, then they upgraded prototype.js to 1.7. After running the Google Chrome memory profiler, it seems that there is a leak of the prototype_event_registry object. I saw a few posts on memory leaks in prototype.js file, and tried all their solutions, but none worked. I had to downgrade back to 1.454.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

 

Mark Trinh edited a comment on JENKINS-10912

Memory leak (?) in dashboard

I'm still getting this error on 1.472. The problem occurred, when they upgraded prototype.js to 1.7. After running the Google Chrome memory profiler, it seems that there is a leak of the prototype_event_registry object. I saw a few posts on memory leaks in prototype.js file, and tried all their solutions, but none worked. I had to downgrade back to 1.454.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Anoop Karollil commented on JENKINS-10912

Memory leak (?) in dashboard

Please disregard all my comments - our leak is on the server side not browser/client side.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira