|New out of memory errors during PDE build? [message #716925]
||Thu, 18 August 2011 19:41
| Nadeem Aboobaker
Registered: July 2009
We recently switched from Eclipse 3.6.2 to Eclipse 3.7 and as a result had to change the way we referenced library jar files in our plugins.|
We used to do this in the plugin.xml:
<library name="../../somefolder/somejar.jar"><export name="*"/></library>
<library name="../anotherfolder/anotherjar.jar"><export name="*"/></library>
It turns out that the "feature" of being able to refer to jar files outside of a plugin was fixed in Bug 342114. So, we changed the way our library jar files get referenced.
Now we use MANIFEST.MF and explicitly list every package in the jar files:
Now when we run the command line PDE build or the build in our development Eclipse, we get "OutOfMemoryError: Java heap space" errors even after significantly increasing our VM memory. We've gone from everything working fine at -Xmx512m to now running out of memory at -Xmx1024m. If increased much past that, then the Eclipse/VM doesn't launch on our 32 bit Windows due to the memory number being too high.
Just a few notes:
- It's not a matter of a few jars and a few exported packages, it's 500+ jar files and 10,000 packages. I understand that's a very high number, but it worked when using plugin.xml and *.
- The PDE still builds correctly when using the plugin.xml way of referring to the external jars, but the runtime does not work (leads to class not found problems).
- There are no problems at runtime with using the MANIFEST.MF approach. Eclipse uses the same memory VM settings as before and things work just as before.
So, my question is, is this a PDE bug that using MANIFEST.MF and listing every package name doesn't work, but doing the same thing with plugin.xml and * works perfectly fine?
[Updated on: Thu, 18 August 2011 19:55]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02239 seconds