Skip to main content
This topic has been closed for replies.

1 reply

D
Dirk Becker
Legend
June 30, 2015

I'd watch memory statistics - both from outside / OS, and inside. For example I recently tracked down a memory leak in an own plugin using OSX instruments.app. Then the InDesign Server scripting object model also exposes some statistics. A debug build as available to plugin developers might also give more insights.

For more details I'd have to dig deeper / beyond the scope of a forum post, as I haven't worked with InDesign Server since 2012.

Btw, $.gc() only has effects within the javascript engine.

In the meantime, could you repeat the test with a server restart rather than $.gc()? Not really appealing, but a server is invoked from the outside anyway...

You probably already ruled out the use of the books feature to combine documents into a single output.

Dirk

Vamitul
Vamitul
Legend
June 30, 2015

If using document.pages.everyItem().duplicate(LocationOptions.AFTER, baseDocument.pages[lastPageIndex])
try doing a document.save(document.fullName) every 50 or so operations, as that will clear the undo stack and significantly improve performance.

D
Dirk Becker
Legend
June 30, 2015

Hmm, InDesign Server and undo stack?

Besides save() has already been mentioned/tried by the OP.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices