Well, it turns out that the combination of a eclipse.ini's weird syntax and Sun JVM's 'alternative' memory handling can give alot of headache.Įclipse.ini is a configuration file that is located in the root of your Eclipse installation which is used as the default arguments passed to Eclipse. query results when running HQL via Hibernate Tools). This would give some more room for extra many open projects and/or using plugins that might need additional memory (e.g. This is ok for most users, but users can tweak these settings by editing eclipse.ini or via the command line, e.g.
Many users seem to have problems with running out of memory when using Eclipse 3.2 in combination with additonal plugins such as those from JBoss Tools or even Eclipse WTP.įor those who just want the solution scroll down to the bottom, you can skip my 'rant' about it.Įclipse default memory settings (at least for Eclipse 3.2) is to run with the following memory settings specified in its eclipse.ini file: Updated 03.08.07: eclipse.ini is sensitive to which line break is used.
