| Eclipse 4.2 memory constantly grows and contracts [message #900216] |
Sun, 05 August 2012 17:03  |
 R Kay
Messages: 2
Registered: August 2012 |
Junior Member |
|
|
I have been an Eclipse user since v. 3.4. I recently made the transition to Eclipse 4.2 from v. 3.7. I use Eclipse with CDT, PyDev, EPIC and Statet plugins.
My OS is WinXP SP3, i686, 3GB
Eclipse version
> Eclipse IDE for Java Developers
> Version: Juno Release
> Build id: 20120614-1722
java -version
> java version "1.6.0_33"
> Java(TM) SE Runtime Environment (build 1.6.0_33-b03)
> Java HotSpot(TM) Client VM (build 20.8-b03, mixed mode)
Ever since I installed v. 4.2, I have noticed that the Eclipse heap status bar keeps growing and contracting in a precise pattern even when I am not doing anything with Eclipse. What is interesting is that my barebones Eclipse 4.2 Java IDE (i.e. clean install without any plugins) does the same thing so I reasonably confident that I don't have a leaky plugin.
So I downloaded VisualVM 1.3.4 and there I can see that the Eden space is where all the memory is growing and contracting. The allocated bytes never make it into the S0, S1, Old or Perm generations. The GC collections are occurring at reliable intervals of time (like every ~30 secs) giving the appearance as a sawtooth graph. I also turned on memory sampling and it appears that most of the allocation activity is occurring in the main (0.5-0.7 MB/sec) and RMI TCP Connection (0.3 MB/sec) threads. The heap histogram reports that most of the memory allocation occurs in the form of org.eclipse.swt.graphics.RGB, byte[], int[], char[] and org.eclipse.swt.graphics.RGB[] objects with the *.RGB classes getting the majority of the allocated bytes.
I tried a heap dump but did not get very far since I don't know what to look for. I am pretty much at the limit of my knowledge.
So my question is why is Eclipse 4.2 furiously allocating bytes even when I am not doing anything with it? It sure seems to be related to the graphics classes but I don't have anything changing in my IDE. I have not seen this behavior with any of the Eclipse 3 releases going back many years. Please help!
Thanks,
RKay
|
|
|
| Re: Eclipse 4.2 memory constantly grows and contracts [message #900293 is a reply to message #900216] |
Mon, 06 August 2012 11:51  |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi,
I think you are seeing
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386070. The next 4.2.1
integration build should have it fixed.
Tom
Am 05.08.12 19:03, schrieb R Kay:
> I have been an Eclipse user since v. 3.4. I recently made the transition
> to Eclipse 4.2 from v. 3.7. I use Eclipse with CDT, PyDev, EPIC and
> Statet plugins.
>
> My OS is WinXP SP3, i686, 3GB
>
> Eclipse version
>> Eclipse IDE for Java Developers
>> Version: Juno Release
>> Build id: 20120614-1722
>
> java -version
>> java version "1.6.0_33"
>> Java(TM) SE Runtime Environment (build 1.6.0_33-b03)
>> Java HotSpot(TM) Client VM (build 20.8-b03, mixed mode)
>
> Ever since I installed v. 4.2, I have noticed that the Eclipse heap
> status bar keeps growing and contracting in a precise pattern even when
> I am not doing anything with Eclipse. What is interesting is that my
> barebones Eclipse 4.2 Java IDE (i.e. clean install without any plugins)
> does the same thing so I reasonably confident that I don't have a leaky
> plugin.
>
> So I downloaded VisualVM 1.3.4 and there I can see that the Eden space
> is where all the memory is growing and contracting. The allocated bytes
> never make it into the S0, S1, Old or Perm generations. The GC
> collections are occurring at reliable intervals of time (like every ~30
> secs) giving the appearance as a sawtooth graph. I also turned on memory
> sampling and it appears that most of the allocation activity is
> occurring in the main (0.5-0.7 MB/sec) and RMI TCP Connection (0.3
> MB/sec) threads. The heap histogram reports that most of the memory
> allocation occurs in the form of org.eclipse.swt.graphics.RGB, byte[],
> int[], char[] and org.eclipse.swt.graphics.RGB[] objects with the *.RGB
> classes getting the majority of the allocated bytes.
>
> I tried a heap dump but did not get very far since I don't know what to
> look for. I am pretty much at the limit of my knowledge.
>
> So my question is why is Eclipse 4.2 furiously allocating bytes even
> when I am not doing anything with it? It sure seems to be related to the
> graphics classes but I don't have anything changing in my IDE. I have
> not seen this behavior with any of the Eclipse 3 releases going back
> many years. Please help!
>
> Thanks,
> RKay
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.08067 seconds
] 
Search
Help
Register
Login
Home
