oXygen Freezes - possibly image related

[Stacey]

Hi There:

oXygen is freezing a lot on me. I have to go into Task Manager and quit the program to resolve the issue.
I can't really pin down what's happening or why, but I think it may have to do with SVG images.
We've replaced all our images with SVG files. I use keys to add them to the documentation.
If I open the .dita file in Notepad++ and edit out the <image>, then I can usually open the file from the .ditamap without issues.
I have no way of identifying what images may cause issues or what needs to be done to them to prevent this from happening. Is there a generic list of requirements that SVGs must adhere to? I would say probably 95% of the images we use don't have this issue; but I'm stuck restarting the application numerous times when I try to wrestle one of the ones that isn't playing nice.
(Can I increase memory or something to help with this issue?)
Thanks,

[Radu]

Hi Stacey,
Not sure, could you tell me more about the cases when Oxygen freezes?
For example does it freeze when you open a DITA XML topic? About how large is that topic? About how many images does it refer? How long does Oxygen freeze in general?
Or does Oxygen freeze when you start typing inside a paragraph?
Or does Oxygen freeze as you are scrolling down in a topic and encounter such an image?
With images in general Oxygen does not attempt to load all images referenced in the topic when you open the topic, it just attempts to compute the width and height of each computed image. With SVG in particular if the <svg> root element has width/height attributes then Oxygen should quickly look at these attributes and use them as dimensions without loading the image itself until you scroll to it.
After an image is loaded Oxygen should cache it to avoid loading it again while you are editing around the image.
Regards,
Radu

[Stacey]

Hi Radu:
I originally took screenshots as PNGs, created an image .ditamap that uses keywords for use with the written content (.dita files) and then our design person recreated the images as .SVGs (using Figma). We gave the images the same names and to update the oXygen content, I basically updated the image map with "svg" replacing "png".
I opened oXygen this morning and it froze immediately, so you don't necessarily need to be doing anything; it freezes when you open certain topics.
This file is 6kb.
I opened the file directly, and I was able to scroll around without issue. I opened the map it's a part of, and I was still able to move around in the .dita file. I closed the file and double-clicked on the link in the map to open it, and it froze.
There are 8 image references in this file. Some would have actual images available in the appropriate folder, some might not (I am expecting to drop a file with the defined name into the folder when it becomes available). I believe I have run into this issue where there are existing images for the keys, which makes me think there might be something corrupt about the image itself that needs fixing.
I replaced all of the images with a known "good" image, closed out of the file, and tried opening it from the .ditamap and it worked without freezing.
When the file was just sitting by itself, it showed me "Key not found" errors for the images, which is what I expect to happen. If it's realizing that there's no linked image when I'm trying to open it from the map, I would expect it to tell me that as an error, not freeze completely.

[Stacey]

I attempted to select another keyref in the attributes pane for one of the images, and it froze when I was doing that. it was a random selection, but it showed the image in the document, so there would have been a linked SVG for it.

[Radu]

Hi Stacey,
Can you prepare a small sample DITA project with which you can still reproduce the problem (couple of those problem SVG images, a small map, a topic, no confidential content) and send it to us (support@oxygenxml.com)?
I can try to work with it on my side and profile the application a bit to see what's going on?

Regards,
Radu