Page 1 of 1

Increased Memory but still running Out of memory

Posted: Wed Jan 25, 2017 8:55 pm
by jeustis

I'm using Oxygen version 18 where I have a transformation on an xml file (2247KB) to create a differently structured xml file. The xsl was unable to complete and resulted in the following error message:

The application exceeded the available memory: 3822MB. To avoid stability issues please restart the application. If the application has become unstable and cannot be closed normally, you can use the Force Quit button from this dialog. Be aware that by doing this you will lose any unsaved documents.
If the problem persists, it is recommended to increase the amount of memory available to the application.

You can increase the memory available to the application by setting a larger value for the -Xmx parameter in the startup script, for example -Xmx5350m.
For more details see the 'Performance problems' and 'Setting a parameter in the startup script' sections of the User Manual.

How to avoid these errors:
In case you were running a diff tool when this problem occurred you can try to use another algorithm next time.
If you just want to inspect a large file, please use the Large File Viewer available from the Tools menu.
Do not keep many editors open, close them when you do not need them anymore.

[ Transformation Performer ] - java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source)
at java.lang.AbstractStringBuilder.append(Unknown Source)
at java.lang.StringBuffer.append(Unknown Source)
at Source)
at Source)
at ro.sync.exml.editor.xmleditor.gc.lyj(Unknown Source)
at ro.sync.exml.editor.xmleditor.gc.myj(Unknown Source)
at ro.sync.exml.editor.xmleditor.gc.fzj(Unknown Source)
at ro.sync.exml.editor.xmleditor.gc$4.the(Unknown Source)
at Source)

I asked for IT help where I work. This person changed the oxygen.bat and oxygenAuthor18.1.vmoptions files.

Xmx2048m -XX:SoftRefLRUPolicyMSPerMB=10 -XX:MaxPermSize=500m


However, there are also Xmx for oxygen18.1.vmoptions, oxgydenAuthor.bat.

Which file do we need to make the change to the Xmx? Thanks for any help or suggestions.


Re: Increased Memory but still running Out of memory

Posted: Wed Jan 25, 2017 9:41 pm
by Costin
Hi Jennifer,

The file where the "Xmx" parameter should be changed depends on how you run oXygen.
You specified that there is an "oxygen.bat" file (where your IT changed the allocated memory through the Xmx parameter) and an "oxygenAuthor.bat" as well. This suggests that you have in fact an oXygen XML Editor installation (which is the flagship product containing both oXygen XML Author and oXygen XML Developer functionality) but are using only oXygen XML Author from it (as it is possible to run only Author or only Developer from the Editor installation).

If that's the case and you are running Author, you should increase the Xmx parameter's value in either "oxygenAuthor.bat" or "oxygenAuthor18.1.vmoptions" file, depending on how you actually run oXygen XML Author.
If you run Author using the executable in the oXygen XML Editor installation folder (oxygenAuthor18.1.exe) or the Author (red A icon) shortcut on your desktop, then the Xmx should be modified in the .vmoptions file. Otherwise, if you are running Author using the startup script (oxygenAuthor.bat) you should modify the Xmx in that .bat file.

Note that oxygenAuthor.bat and oxygen.bat are 2 different files, for different situations: the 1st one is for Author and the 2nd one is for the main/flagship product Editor. So if you start Author through the bat startup script, you modify "oxygenAuthor.bat". If instead you start Editor through the startup script (not by executable or desktop shortcut) you modify "oxygen.bat".

Otherwise, if you start either Author or Editor using the executable or the desktop shortcuts, you should modify their corresponding .vmoptions file (either "oxygenAuthor18.1.vmoptions" or oxygen"18.1.vmoptions").

However from your report, even if it is not clear what exactly you are running, it seems that you already have allocated 4GB of memory to the application:

Code: Select all

The application exceeded the available memory: 3822MB.
Is the document you are trying to transform (publish) on a single line?
Or does it contain a very large number of lines and possibly bi-directional text?

If possible, please send the complete out of memory report you obtain right from oXygen to our official support email address: support AT oxygenxml DOT com and, if possible, send us the file you are trying to transform to analyze what happens there.


Re: Increased Memory but still running Out of memory

Posted: Mon Jan 30, 2017 12:05 pm
by SathyaOX
Similar error prompts for me. I use oXygen Author 17.1 and I have increased the memory in oxygenAuthor17.1.vmoptions file.

Re: Increased Memory but still running Out of memory

Posted: Mon Jan 30, 2017 12:45 pm
by adrian

@Sathya: "Out of memory" is a very generic error. Increasing the available heap memory can resolve the issue when you are indeed working with large files or a hierarchy of many files, but that may not always be the solution.
If Oxygen runs out of memory when you apply an XSLT transformation, the problem is usually with the XSLT stylesheet.

So the question is, what operation are you running when Oxygen runs out of memory?


Re: Increased Memory but still running Out of memory

Posted: Mon Jan 30, 2017 3:10 pm
by SathyaOX
The error prompts when we work on a long file conref file. we just increase the memory and restart the oXygen application.

Re: Increased Memory but still running Out of memory

Posted: Mon Jan 30, 2017 3:56 pm
by adrian

Does that resolve the issue?
Check in Help > About (last row, Total), if the memory increase is in effect.
If the issue persists, have you considered reporting it to


Re: Increased Memory but still running Out of memory

Posted: Tue Jan 31, 2017 6:55 am
by SathyaOX
The memory change reflects in Help. This issue raises only when we work on large project file that contains many (approx. 700+) conref files. Some times the oXygen screen appears black and restarts automatically. For the other guides, there is no issue. I didnt get in touch with oXygen support team.

Re: Increased Memory but still running Out of memory

Posted: Thu Jun 28, 2018 5:45 pm
by surighanta

This made me nuts for a while, but root of the problem was really peculiar in my case. It was missing of a tag closing which eventually showed this error in the error dialogue. After trying with bare xalan, i figured out the issue and after fixing the closing tag it worked in oxygen also like a charm.