Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318705

Summary: Out of memory during: "Contacting Software Sites".
Product: [Eclipse Project] Equinox Reporter: Massimo Roscio <m.roscio>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: henrik.lindberg, m.roscio, Olivier_Thomann
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Stack trace none

Description Massimo Roscio CLA 2010-07-02 08:39:18 EDT 
Build Identifier: eclipse.buildId=M20100211-1343

java.lang.OutOfMemoryError: Java heap space
at java.lang.String.<init>(String.java:208)
at com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java:226)


Reproducible: Always

Steps to Reproduce:
1.Start Eclipse
2.Go to Help
3.Select Check for updates
Comment 1 Massimo Roscio CLA 2010-07-02 08:42:55 EDT 
Created attachment 173298 [details]
Stack trace
Comment 2 Olivier Thomann CLA 2010-07-02 10:00:13 EDT 
Moving to Equinox/p2
Comment 3 Henrik Lindberg CLA 2010-07-03 23:57:50 EDT 
Well, it is telling you that you ran out of memory in the Java VM. Just because it happened when checking for updates does not mean that it was p2 that took all your memory. The stack trace reveals that it is simply trying to parse an XML document.

If you have lots of things installed in your IDE already, you probably want to increase the max memory available to the VM.

Does this happens when checking for updates on a freshly started IDE where no editors are open?

Do this:
1. Close all open editors in your IDE
2. Exit
3. Start
4. Check for updates

The reason for doing this is that if you have lots of things open, a lot of memory can have been consumed already. Some plugins could be buggy and leak memory, etc.

Second thing to check is if you are trying to read a repository that has errors or simply is *enormous".

I am tempted to close as "not-p2", but if this happens on a fresh Helios configuration while only contacting eclipse repositories it is something that should be looked into. Can you provide more details?
Comment 4 Massimo Roscio CLA 2010-07-06 06:07:29 EDT 
Thank you for your reply.
In fact I have gradually increased Xmx from 384 to 768 MB, ie

C:\Programmi\eclipse-SDK-3.5.2-win32\eclipse\eclipse.exe -vmargs Xmx768M

If the stack trace is not enough, what diagnostic tools could I use to look at what is happening?
Since this is a fresh installation - I have been using 3.4.2 until last Thursday - querying sites for updates and plugins is the first thing I do after having started Eclipse.

I'd be really obliged if you could help me in performing a real troubleshooting.

Sincerely,
Massimo
Comment 5 Massimo Roscio CLA 2010-07-07 05:24:29 EDT 
Trying to install Eclipse Memory Analyzer (MAT) always fail:

eclipse.buildId=M20100211-1343
java.version=1.5.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT
Command-line arguments:  -os win32 -ws win32 -arch x86


Error
Wed Jul 07 11:21:06 CEST 2010
No repository found at http://download.eclipse.org/technology/mat/0.8/update-site/.

How can I check what wastes all the JVM virtual memory?
regards
MR
Comment 6 Massimo Roscio CLA 2010-07-07 05:46:15 EDT 
Found repository for MAT version 1.0, downloaded.
Install procedure fails for lack of heap space.
I understand that something in my IDE is poorly handled by Eclipse, which wastes memory instead of reporting an error.
How can I detect what is wrong?
Thanks, regards
MR
Comment 7 John Arthorne CLA 2010-08-06 09:29:00 EDT 

*** This bug has been marked as a duplicate of bug 314118 ***