FrameMaker2019 no responding during searching & store elements by ExtendScript

[Cheng-T]

During searching & store elements by ExtendScript under FM2019,  FrameMaker is hung up only with the big book, but not small book. Any ideas?  thanks. 

[Cheng-T]

We use "new Object" and "new Array" to store all necessary information. 

Which part of memeory is used by Extends ript? Is there any limitiation for memory usage? 

[frameexpert]

What are you searching for and storing? It's hard to know what the issue might be without more details on what your script is doing.

[JonBe]

Hi,

Are you using the 32 or 64 bit version of 2019? Does FrameMaker eventually respond?

There was a bug with Extendscript and FrameMaker versions prior to 2019 where walking the element tree using recursion would result in FrameMaker increasing memory use, until it reached the limit on 32 bit systems (aprox 2GB?), when it would crash. In the custom structured application my customer uses, this occured with about 50,000 elements. I created a bug report for this on https://tracker.adobe.com/#/home. I still see the increase in memory on 64 bit systems, however the limit is higher. I have also moved away from using recursion.

The other thing FrameMaker still does, is that with long running scripted or plugin processes, it stops updating the UI, and appears to have hung. I have implemented a progress screen for my customers, that gives the appearance of progress (;-)), to stop eager users aborting FrameMaker.

HTH!

Jon

[kglad]

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post if it helps you get responses.

<"moved from using the community">