• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

FrameMaker2019 no responding during searching & store elements by ExtendScript

Community Beginner ,
Sep 08, 2023 Sep 08, 2023

Copy link to clipboard

Copied

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

 

Views

116

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 08, 2023 Sep 08, 2023

Copy link to clipboard

Copied

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? 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 08, 2023 Sep 08, 2023

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Sep 25, 2023 Sep 25, 2023

Copy link to clipboard

Copied

LATEST

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 08, 2023 Sep 08, 2023

Copy link to clipboard

Copied

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">

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines