Eclipse Community Forums: DSDP - Real-Time Software Components (RTSC) » java.lang.OutOfMemoryError: Java heap space -- help

Home » Archived » DSDP - Real-Time Software Components (RTSC) » java.lang.OutOfMemoryError: Java heap space -- help

java.lang.OutOfMemoryError: Java heap space -- help [message #714494]

Wed, 10 August 2011 12:23

Eclipse User

I have the following problem. Any idea?
I have already increased the heap size to 1024MiB (MK_BLDOPTS=--Xmx1024m)

generating custom ti.sysbios library makefile ...
generating custom ti.sdo.ipc library makefile ...
using Library lib/Release/ti.drv.edma3.drv.ae66
using Library lib/c6616/Release/ti.drv.edma3.rm.ae66
java.lang.OutOfMemoryError: Java heap space
at
com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.getNodeObject(DeferredDocumentImpl.java:1103)

at
com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.synchronizeChildren(DeferredDocumentImpl.java:1777)

at
com.sun.org.apache.xerces.internal.dom.DeferredElementNSImpl.synchronizeChildren(DeferredElementNSImpl.java:183)

at
com.sun.org.apache.xerces.internal.dom.ParentNode.hasChildNodes(ParentNode.java:231)

at
com.sun.org.apache.xerces.internal.dom.DeepNodeListImpl.nextMatchingElementAfter(DeepNodeListImpl.java:207)

at
com.sun.org.apache.xerces.internal.dom.DeepNodeListImpl.item(DeepNodeListImpl.java:182)

at
com.sun.org.apache.xerces.internal.dom.DeepNodeListImpl.getLength(DeepNodeListImpl.java:153)

at xdc.services.global.XML.getList(XML.java:65)
at xdc.services.global.XML.getList(XML.java:55)
at xdc.services.global.Vers.readList(Vers.java:503)
at xdc.services.global.Vers.getTargetReferences(Vers.java:140)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:592)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:161)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:247)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3330)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2487)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:164)

at xdc.services.intern.xsr.Invoke.call(Invoke.java:127)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3330)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2487)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:164)

at xdc.services.intern.xsr.Invoke.call(Invoke.java:89)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3330)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2487)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:164)

at
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:398)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3065)
at
org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:175)

at org.mozilla.javascript.Context.evaluateReader(Context.java:1135)
at config.Shell.evaluateReader(Shell.java:813)
Exception in thread "main" gmake.exe: ***
[package/cfg/xyz_release_e66_pe66.xdl] Error 1

Re: java.lang.OutOfMemoryError: Java heap space -- help [message #714576 is a reply to message #714494]

Wed, 10 August 2011 18:50

Eclipse User

Patrick,
Are you working in CCS or on the command line? Can you set the environment variable XDC_TRACE_ENABLE to 'all' and post the output?

Re: java.lang.OutOfMemoryError: Java heap space -- help [message #714670 is a reply to message #714576]

Thu, 11 August 2011 04:35

Eclipse User

from the command line. I will send you the log.

Sasha Slijepcevic wrote:
> Patrick,
> Are you working in CCS or on the command line? Can you set the
> environment variable XDC_TRACE_ENABLE to 'all' and post the output?

Re: java.lang.OutOfMemoryError: Java heap space -- help [message #716296 is a reply to message #714670]

Tue, 16 August 2011 20:02

Eclipse User

The error happened while the files 'package/package.bld.xml' were read from each package loaded during the config step. Each of these files is then examined for its package's build properties using Java DOM API. I can't tell if you are processing a file of 100MB in size, and I can't imagine any of package.bld.xml files would be that big, or XDCtools is not releasing memory properly after these files are processed.

Can you check if there is a file nash_femtoPHY_core1_release_e66_pe66.cfg.xml in your package/cfg subdirectory? If there is, that file is possibly incomplete. If you can send that file to me, and with the help of the trace output you sent me before, I may be able to detect which package is causing the problem.

I don't have a clean workaround for you right now. You could probably disable the code that reads package.bld.xml files, but you would have to change some files inside of your XDCtools installation. I'll look into the options further.

Previous Topic:	exportSrc
Next Topic:	Problem with RTSC module primer lesson 5

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Aug 30 23:22:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter