Page 1 of 1

performance issues on Mac

Posted: Wed Jan 30, 2019 8:13 pm
by bmorgan888
I am running Oxygen XML Editor 19.0, build 2017062918 on a Mac with High Sierra v10.13.6.

I am creating and editing DITA source files and map files.

Oxygen is giving me performance issues lately, I can’t drag and drop files from Project pane into Map files, ability to minimize the Project pane is inconsistent.

Are there any compatibility issues causing this?

Re: performance issues on Mac

Posted: Thu Jan 31, 2019 12:42 pm
by Radu
Hi,

Do these problems still manifest after you restart Oxygen?
How about if you go and reset the views layout from the main Oxygen menu "Window->Reset layout"?
By "performance problems" do you also mean delays when editing or are the problems restricted to this drag and drop problem?

Regards,
Radu

Re: performance issues on Mac

Posted: Wed Mar 06, 2019 9:41 am
by alice434
After running Oxygen XML Editor on my MacBook Pro, it seems the performance of the system is too slow, I thought it may be the system problem so, I contacted Apple technical service but there I got to know that system is absolutely fine then what is the exact issue?

Re: performance issues on Mac

Posted: Wed Mar 06, 2019 10:14 am
by adrian
Hello Alice,

What version of Oxygen are you using (Help > About)?
What MacBook Pro model are you using? How much RAM does it have installed?
After running Oxygen XML Editor on my MacBook Pro, it seems the performance of the system is too slow
Could you please clarify what "too slow" means in this context. Is the system slowing down while Oxygen is running? Or is Oxygen slow to respond to commands?

Regards,
Adrian

Re: performance issues on Mac

Posted: Tue Jul 02, 2019 3:10 pm
by dgibbs
I am also experiencing very poor performance from Oxygen.

Trying open 271Kb xml document takes extremely long or just doesn't load. Have to open xml up in another text editor which happens virtually instantly.

When deleting sections of content using the the outline palette, after deleting a few (maybe 5), Oxygen hangs, and sometimes recovers, else I have to force quit, and edit in another text editor.

MacBook Pro, ,3 GHz Intel Core i5, 8 Gig Ram.
<oXygen/> XML Editor 21.0, build 2019040204

Is there anything I can configure or do to make Oxygen faster?

Damian

Re: performance issues on Mac

Posted: Wed Jul 03, 2019 9:23 am
by Radu
Hi Damian,

Does Oxygen issue any warning when opening the file? For example does it report that it has very long lines or some special characters inside?
In the Oxygen Preferences=>"Editor / Open" there is a "Support for special characters" setting, if you set it to "Disable support" and re-open the XML file does the performance increase?

Regards,
Radu

Re: performance issues on Mac

Posted: Wed Oct 23, 2019 4:36 pm
by dgibbs
Hi Radu

I have tried suggestions: restarting Oxygen, restarting computer, Disable support for special characters in preferences.

The strange thing is it runs OK for a while (never been snappy), but then every now and then, seems to be after opening an xml document larger than about 1 Mb, it becomes really slow and unusable.

I've just restarted Oxygen 3 times and finally seeming to be operating at a useable speed again.

Any further suggestions for optimising for speed?

Many thanks
Damian

Re: performance issues on Mac

Posted: Wed Oct 23, 2019 5:46 pm
by dgibbs
Radu wrote: Wed Jul 03, 2019 9:23 am Hi Damian,

Does Oxygen issue any warning when opening the file? For example does it report that it has very long lines or some special characters inside?
In the Oxygen Preferences=>"Editor / Open" there is a "Support for special characters" setting, if you set it to "Disable support" and re-open the XML file does the performance increase?

Regards,
Radu
This does seem to be the case. It seems that an XML document "contains bidirectional text (such as Arabic or Hebrew), South/South-Eastern Asian text, or special characters (such as combining characters) that require special handling to ensure proper editing." and you "Enable" support, Oxygen is extremely slow even if the document is a few lines.

Is there any way to check a document for special characters after it has been opened in Oxygen Editor?

Damian

Re: performance issues on Mac

Posted: Thu Oct 24, 2019 5:24 pm
by adrian
Hi,
Is there any way to check a document for special characters after it has been opened in Oxygen Editor?
If you disabled the support for special characters, but want to know if the document requires it, check in the Properties view (Window > Show View > ...) for the "BIDI" property. If it's "true" then it contains special characters that would trigger the special characters mode.

If you want to locate the actual characters that trigger it, check for Radu's answer on the topic How to find special characters?.
Radu wrote:There is an Oxygen GitHub project containing lots of sample plugins which you can download as a zip:
https://github.com/oxygenxml/wsaccess-j ... le-plugins

I just uploaded there a plugin folder called "determineComplexLayoutChars" which can be copied to the "OXYGEN_INSTALL_DIR\plugins" folder. After you start Oxygen the plugin will add a new contextual menu action when an XML document is opened in the Text editing mode. This new "Determine Complex Layout Chars" action should run a detection and then report all characters in the results view.

A quick and dirty, but less exact way, to find the causing characters is to search for "Combining characters" (Unicode range 0300–036F). Use Find/Replace with "Regular expression" enabled and "[\u0300-\u036f]" (without the quotes). Combining characters are the most encountered and elusive type of characters that trigger the bidirectional text support.

If you can't find anything in the range of "Combining characters" and you know that there shouldn't be any special characters in the file, but suspect a random mistake in the text, try the entire Unicode non-ASCII range [\u0100-\uffff]. Note that very few characters from this range actually trigger BiDi, but it should at least provide a clue if something accidentally slipped by in the text.

If you work with actual right-to-left scripts (or special glyphs) then the above may not be of much help as most right-to-left scripts trigger the bidirectional text support because they actually need it.

Regards,
Adrian