I'm trying to populate a few thousands of PDF forms with around 100 fields per file. In Python it looks like this:
This additional time allows system to close Acrobat app and clear all garbages from memory, but waiting 20 second every few minutes is not too efficient.
Do you maybe know some other way how it can be resolved? Something like forcing Actobat to clear cache without closing it or maybe just using some different functions to populate forms?
Acrobat is an interactive tool with tools for very low volume automation. Never mind 200 per minute, 200 is too many. Restart Acrobat at least every 100 files and check results carefully.
Everything said above, and you probably want to put something in place to make sure that Acrobat has actually exited fully before you start again.
Sorry, but for me it is just a set of bugs in SDK and not something to deal with it.
First of all: any software should not leave trash in a memory after closing files. If from some reasons you have to leave references to closed files, then you should give user at least option to force some garbage collector or clear cache.
Second: if user is asking to close application it should be closed without keeping it hidden in a background to "open" it once again with all garbages from previous run.
SDK does not have any problems with populating files to fast, it is just crashing after populating too many fields. To be clear this "too many" fields is something that average laptp is able to populate literally in a less thatn 5 minutes. It really looks like software bug and not something that user shoud be worry about. We are talking here about paid comercial software that should not be crashing by defaulf after 5 minutes of using it.
Of course it's a set of bugs. Some of them have been there for 20 years, others are newer. We have spent years working around them. It's no use telling us it should be better. You could try reporting it to Adobe, but my suggestion is to look for a tool more suitable. Or complain to Adobe, not your fellow sufferers.
Ok, I will try to report it as bugs(leaving trash in a memory and not closing app), but from this what I already see probably it will be much easier just to find some other software. Fortunately I was only checking benefits from moving users from nitro pro to acrobat pro. Idea was to add them not only edit PDF options, but also a few extra tools based on SDK (simple python scripts to run on their computers), but if it is crashing by default I will look for something more stable and not server based.
You are using Acrobat as an automation server. Not only is this against the license agreement, it's not suitable for the task (as you've already discovered). You should be using a PDF Library or form filling tool. Both Appligent and Active PDF make tools specifically for this purpose. And there are many others.
Right... if I'm using one thread in a laptop to convert small excel file to PDFs during cofee break(less than 10 minutes) this is "automation server". xD Just please don't go with such idea to the microsoft as then they can move "mail merge" option from word to windows server. Are you really thinking that using some SDK for more than 5 minutes requires moving it to the server? Or maybe not leaving trash in a memory should require additional license?