Enterprise Editor v24 Build build 2021121518 Unresponsive With JSON FIle

[Jamil]

I performed a conversion of an XML document to JSON. This took some time to complete, but the editor never responded again even after opening the json file in a new tab. The XML document is about 67MB. I have to manipulate it in JavaScript, and json is simpler in this case. It seems the large json file causes issues for this version of the editor. Even with the file open, it is completely unresponsive. I did allocate 8GB in vmoptions. There's plenty of memory available, but the json appears to cause this issue.

[teo]

Hi Jamil,

I tried to reproduce the problem on large files (50-60 MB), but I did not succeed.
All XML to JSON conversions were performed eventually, although in some cases it took several tens of seconds.
And the resulting JSON files did not make the editor unresponsive.

If there are no issues / restrictions on the contents of your files, could you provide us with a sample JSON file (or the XML used for conversion) that caused problems to you?
We would greatly appreciate it and it would be a good starting point in our investigation.
You can use this form, https://www.oxygenxml.com/techSupport.html, which makes it easy to upload large files.

Kind regards,
Teo

[Jamil]

I just reproduced the issue and will send the XML I converted to JSON using oxygen editor. I did it via Tools|JSON|XML to JSON on the menu. If you leave open JSON document in editor checked off, the application freezes forever and never responds. It has something to do with the JSON file it created. If I open the converted JSON file alone, the editor will also freeze and never respond.

[teo]

Hi Jamil,

I reproduced the problem when trying to convert the file you sent.
As I commented on other thread started by you recently (viewtopic.php?p=64630#p64630), it seems a regression compared to older versions.
I have already registered the issue for investigation.

Regards,
Teo

[Jamil]

So it seems release 23 broke several items related to JSON. v22 is stable regarding this.
I will look to uninstall v24 and reinstall v22.