Description of problem: Often times, when running Eclipse in FC6, I get OOMs from gij. I don't know how we can track this down, but it seems to be pretty reproducible. I've had this happen on both x86 and x86_64. Version-Release number of selected component (if applicable): gcc-4.1.1-30 How reproducible: Seemingly random. Steps to Reproduce: 1. Start Eclipse (eclipse) in FC6 from the command line 2. Work (try some Java projects, check out some Eclipse plugins, etc.) 3. Hope for an OOM Actual results: GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! *** Catastrophic failure while handling uncaught exception. GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! *** Catastrophic failure while handling uncaught exception. GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! *** Catastrophic failure while handling uncaught exception. Expected results: No errors, no OOMs. Additional info:
I'm seeing out of memory errors thrown by libgcj when running eclipse (eg, updating Classpath) using the gcj-eclipse RPMs. I don't seem to have debuginfo so the stack traces for libgcj are missing.
In my case I already have a classpath checkout, so I choose Team->Update or whatever that is called. You can probably reproduce the OOM by following the classpath-in-eclipse instructions http://developer.classpath.org/mediation/ClasspathHackingWithEclipse
I've tried to use those instructions, but I couldn't do anything. The build runs for a while and then halts with an error. Unfortunately, it clears the Console window so I can't see what the error was. I'd love to get to the bottom of this one, but as far as I can see it's unreproducible.
OK, I fixed that one, but I still can't get OOM. When you find a way do do this that is reproducible, I'll have another look.