Community
Participate
Working Groups
Created attachment 82254 [details] jbuilder init file Build ID: M20070212-1330 Steps To Reproduce: I'm running Jbuilder 2007 which is based on eclipse 3.2.2.r322_v20070119-RQghndJN8IM0MsK (build M20070212-1330), after a number of times that my europa version of eclipse crashed while playing with GMF. 1) I created an example plugin following the instructions in: http://www.onjava.com/pub/a/onjava/2005/02/09/eclipse.html?page=1 2) Tried to test the example (and pretty slim) plugin by clicking on "Launch an eclipse application" on the plugin.xml file, overview tab. 3) The new eclipse instance goes up, and in the console from where the instance was called I get "Exception in thread "Java indexing" java.lang.OutOfMemoryError: Java heap space" More information: I reproduced this bug many times. I had no time to try to reproduce it in the europa eclipse version, but I am also getting there a lot of eclipse crashed because of overallocation of memory. Tried to increase the ammount of heap as explained in bug 92250 but still didn't help.
Stack: Exception in thread "Java indexing" java.lang.OutOfMemoryError: Java heap space at org.eclipse.jdt.internal.compiler.util.HashtableOfObject.<init>(HashtableOfObject.java:39) at org.eclipse.jdt.internal.compiler.util.HashtableOfObject.rehash(HashtableOfObject.java:139) at org.eclipse.jdt.internal.compiler.util.HashtableOfObject.put(HashtableOfObject.java:112) at org.eclipse.jdt.internal.core.index.DiskIndex.copyQueryResults(DiskIndex.java:325) at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java:489) at org.eclipse.jdt.internal.core.index.Index.save(Index.java:178) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:588) at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute(AddJarFileToIndex.java:200) at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:372) at java.lang.Thread.run(Thread.java:619)
If you enable the heap monitor (on the general page) you can get an idea of how big what you are running is. What else do you have installed beside the SDK? The OutOfMemory error is happening in JDT Core. I have seen this myself during Java Indexing now and again
Definitely looks as a duplicate of 166223 which was fixed in 3.3. However, I was not able to reproduce the OOME following the comment 0 scenario. One thing is not clear in this scenario: JBuilder is using Eclipse 3.2.2 and you're talking about Europa version which is based on Eclipse 3.3!? Tod, can you describe your scenario to reproduce the problem and help me to verify that it's fixed using Eclipse 3.3? Thanks *** This bug has been marked as a duplicate of bug 166223 ***
Frederic I am seeing this in 3.4 but not all of the time. STEPS 1) Load platform-ui and platform-ui-tests module from HEAD 2) Self host 3) In the self hosted workspace select Import-Existing Plug-ins 4) Select source 5) Select ide and workbench 6) Hit finish 7) The wizard will finish and a build will kick off. At this point the build will fail.
(In reply to comment #4) > Frederic I am seeing this in 3.4 but not all of the time. > > STEPS > 1) Load platform-ui and platform-ui-tests module from HEAD > 2) Self host > 3) In the self hosted workspace select Import-Existing Plug-ins > 4) Select source > 5) Select ide and workbench > 6) Hit finish > 7) The wizard will finish and a build will kick off. At this point the build > will fail. > What -Xmx do use while launching your self hosted workspace? That does not look like the same issue as the OOME occurred in indexing. IMO, you should open a new bug for this issue...
I am using the default settings. I'll open another bug next time I see it.
(In reply to comment #6) > I am using the default settings. > > I'll open another bug next time I see it. > OK, thanks
See Bug 209065 for my issue
Verified for 3.4 M4 using build I20071211-0010
