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

Bug 314790

Summary: Default JVM memory not enough for cdoc
Product: [Technology] RTSC Reporter: Amit Mookerjee <amitm>
Component: CoreAssignee: Joseph Cusano <jcusano>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: d-russo, dfriedland, felix.otto
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: target:3.40

Description Amit Mookerjee CLA 2010-05-27 19:08:06 EDT 
In certain cases the cdoc tool requires more than the default memory allocated to it by the JVM. This causes the tool to fail. This problem can be reproduced in the xdcprod tree by executing cdoc on the  XDCtools repository.

xs  xdc.tools.cdoc -od:exports/docs/cdoc -s -Pr product/Windows/$(MAJMIN)/packages

Increasing the maximum amount of heap space allocated to xs via the "--Xmx" option can workaround this problem. In the xdcprod tree --Xmx1024m (maximum heap space for program is 1024 mega bytes!) option is used with cdoc. Memory consumption by cdoc needs to be reduced.
Comment 1 Felix Otto CLA 2015-03-12 10:24:52 EDT 
It's not only a workaround for a certain toolset but generally required. I have seen couple of times, that Eclipse got almost stuck while calculating dependencies during the installation/update of features. During this time the memory consumption was greater than 512MB.

So 1g instead of 512m will help to prevent update issues.

http://scn.sap.com/community/abap/eclipse/blog/2015/03/12/abap-development-tools-version-241-available-now-on-our-updatesite#comment-571736
Comment 2 Felix Otto CLA 2015-03-24 05:42:25 EDT 
The default value will be increased with Eclipse Mars
http://www.eclipse.org/eclipse/news/4.5/M6/#Platform