Oxygen XML Forum

Using oXygen on Ubuntu Lucid 64-bit with a quad-core processor and 8GB of RAM.

I've been trying to get used to oXygen 11.2 for a few weeks now, and I've finally given up and reverted to 10.3. These are the problems I'm having:

• The application locks up after a couple of hours of use, and at the same time seems to lock up other Java applications which are running on the system
• Every now and then, oXygen will refuse to open any files, either when double-clicking them in the project explorer pane or by using File / Open. It has to be restarted before it will open files.
• Ordinary operations are painfully slow. For instance, pressing Control + F to bring up the Find dialog is so slow that I often find I've typed a series of characters into the file I'm editing by mistake, because the Find dialog was so slow to show up. The same applies to Control + E to insert a tag.

In contrast, 10.3 is very well-behaved and responsive.

I only use oXygen Editor, not Author. This is my vmoptions file:

-Xss512m
-Xmx2048m
-Dcom.oxygenxml.language=English

I originally ran it with the same settings as 10.3:

-Xss64m
-Xmx700m
-Dcom.oxygenxml.language=English

but it was even worse.

Is anyone else seeing the same behaviour? Any suggestions for a fix?

Hello,

If you have downloaded, unpacked and ran the 'All platforms' kit of oxygen(oxygen.tar.gz) then Oxygen might have ran with the OpenJDK Java virtual machine. Oxygen is incompatible with OpenJDK and requires Java SE from Sun. This JRE from Sun is included in the Linux installation kit of Oxygen(oxygen.sh) so if you haven't already then please try downloading and installing this one(the 64-bit kit).

Check what JVM is Oxygen using in Help -> About, System properties. Look for:
- java.runtime.name should be Java(TM) SE Runtime Environment
- java.runtime.version should be 1.6.0_16-b01
- sun.boot.library.path should point to <oxygen-installation-folder>/jre/bin[/amd64]

1. The fact that other Java applications freeze together with Oxygen most probably means that they share the same JVM and they shouldn't because Oxygen comes bundled with its own JVM so it should run separately without interference to/from other Java applications.

2. and 3. These point to the same fact that it's using the wrong JVM(which is not a Java SE) and not the bundled one.

Also, regarding the vmoptions files:
a. -Xss specifies the stack size for any thread and should probably never exceed 16m, actually 1m should be more than enough. 512m shouldn't even run and if it did it would probably use huge amounts of memory(512MB per thread multiplied with 30 threads => 15GB).
b. I believe you meant to set -Xms, the initial heap size, to 512m which is correct though probably unnecessary.

Also be aware that the oxygen.vmoptions file is only used when running Oxygen with the 'oxygen'(no extension) script or the Desktop shortcut, not the oxygen.sh script.

Please let me know of any progress you have made.

If the problems keep persisting then please send us a problem report(Help -> Report problem) to allow us to better investigate its cause.

Regards,
Adrian

Hi there,

I have tried running 11.2 with both the OpenJDK (which is my default) and the Sun JRE which is in the oXygen directory. I'd ended up with the OpenJDK because it was causing fewer lockups, but I've now switched back to the bundled JRE.

The - sun.boot.library.path points to <oxygen-installation-folder>/jre/lib/amd64, not /bin/, but I'm assuming that's a typo.

I've set my vmoptions file to

-Xms512m
-Xmx2048m

and I'll run it for a few days and see how it goes.

Thanks for your help,
Martin

Hi,

martindholmes wrote:I have tried running 11.2 with both the OpenJDK (which is my default) and the Sun JRE which is in the oXygen directory. I'd ended up with the OpenJDK because it was causing fewer lockups, but I've now switched back to the bundled JRE.

OpenJDK is not supported by Oxygen, it has a number of issues that make some dialogs unusable or can even lock the application.
Oxygen was supposed to give a warning at startup when ran with OpenJDK but it seems it got lost in the implementation. We'll fix this and in the next build of 11.2 it will give a warning.

martindholmes wrote:The - sun.boot.library.path points to <oxygen-installation-folder>/jre/lib/amd64, not /bin/, but I'm assuming that's a typo.

Yes, that was a typo on my part.

Let us know if you encounter further issues.

Regards,
Adrian