oxygen 12.0: 1 CPU core at 100% when it should be idle

Having trouble installing <oXygen/>? Got a bug to report? Post it all here.
ojeulin
Posts: 17
Location: Paris, France

oxygen 12.0: 1 CPU core at 100% when it should be idle

Tue Nov 16, 2010 8:31 pm

Hello,

here is my problem:
I'm working with oxygen 12.0 (editing XML/XSLT in text mode, running a few XSLT). After some time (maybe 1 hour, I don't know exactly) the java process of oxygen suddenly uses 100% of one core of the CPU.
So far, this happens every time I use oxygen. I never had this kind of problem with the previous versions.

This happens even when I do nothing in oxygen. It's just opened, I'm not even using it, and suddenly I see that the CPU usage is at 50% (100% of 1 of the 2 cores).
There is no XSLT or XPath running. The UI is responding normally, I don't feel any lag. I really don't know what is causing this...

(There is only one instance running)

OS:
ubuntu 10.10 – Linux 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 i686 GNU/Linux

RAM: 3 Go

java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)

command line:
java -Xss512k -Xmx1500m -XX:SoftRefLRUPolicyMSPerMB=10 -Dcom.oxygenxml.editor.plugins.dir=/usr/local/Oxygen/plugins -Dcom.oxygenxml.MultipleInstances=true -XX:MaxPermSize=256m -cp /usr/local/Oxygen/lib/oxygen.jar:/usr/local/Oxygen/classes:/usr/local/Oxygen ro.sync.exml.Oxygen
adrian
Posts: 2453

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Wed Nov 17, 2010 1:38 pm

Hello,

This could be a Java Virtual Machine(JVM) problem.
To see what JVM is used for running Oxygen go to Help -> About -> System Properties. Look for the properties "java.home", and "java.vm.*"(all that start with "java.vm.").

For Linux Oxygen only supports Java SE from Oracle/Sun, it will not run properly with the GNU, OpenJDK or other open source JVMs.

If the properties point to a different JVM/JRE than the expected one, please alter the scripts, command line or path to use the appropriate Java SE JRE.


To avoid JVM problems you can simply download and install the Linux(32-bit in your case) distribution. This has a built-in JRE that has been tested extensively with Oxygen. You can find it on our web site:
http://www.oxygenxml.com/download_oxygenxml_editor.html (Linux tab)
To adjust JVM options for this distribution you can edit the .vmoptions file corresponding to the launcher.

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
ojeulin
Posts: 17
Location: Paris, France

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Wed Nov 17, 2010 4:48 pm

Code: Select all

java.home   /usr/lib/jvm/java-6-sun-1.6.0.22/jre

java.vm.info   mixed mode
java.vm.name   Java HotSpot(TM) Server VM
java.vm.specification.name   Java Virtual Machine Specification
java.vm.specification.vendor   Sun Microsystems Inc.
java.vm.specification.version   1.0
java.vm.vendor   Sun Microsystems Inc.
java.vm.version   17.1-b03

(I also use jedit, with the same JVM, and I don't have this kind of problem)
ojeulin
Posts: 17
Location: Paris, France

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Wed Nov 17, 2010 4:49 pm

I'll try the Linux distribution.
ojeulin
Posts: 17
Location: Paris, France

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Wed Nov 17, 2010 6:48 pm

I still have the problem. :?
adrian
Posts: 2453

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Wed Nov 17, 2010 6:55 pm

To help us analyze the source of the problem, please send a problem report from the Oxygen GUI(Help -> Report Problem) after the issue has occurred.

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
ojeulin
Posts: 17
Location: Paris, France

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Mon Nov 22, 2010 1:45 pm

Report sent. Thanks for your help.
adrian
Posts: 2453

Re: oxygen 12.0: 1 CPU core at 100% when it should be idle

Tue Nov 23, 2010 6:01 pm

In case anyone else encounters this issue, this turned out to be a "stuck" JVM thread("Direct Clip") that handles sound. This is part of the JVM but it is started after a sound event is issued by Oxygen.

This is triggered whenever the status message notifies an operation has finished(e.g. after a transformation or a validation) if the option "Beep on operation finished" is enabled in Options -> Preferences -> Global(first item). Disabling this option resolved the problem.

We'll replace this sound notification with a simple system beep in the next release of Oxygen to avoid such problems.

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

Return to “Common Problems”

Who is online

Users browsing this forum: No registered users and 5 guests