Hey folks,
I used Livecycle Designer ES 8.2 to create a two-page form for job specifications, complete with numerous text boxes, radio buttons, check boxes and a few small scripts using Javascript (just for changing the presence of a subform). The PDF (or rather Adobe Acrobat 7 and 9 Pro) seems to use a ton more memory than when viewing other similar forms, around 250MB, and saving the PDF pushes it as far as 600MB and takes about six seconds on my machine. Worse yet, Adobe Acrobat 7 Pro on other machines just about completely hangs our takes up to 30 seconds to complete a save. The form is to be filled out and saved, so I'm not really using any client/server or XML functionality - just a basic form to keep track of details basically. The form doesn't change the layout at all except for changing the presence of a few subforms back and forth between visible and invisible.
Is there a way to optimize the PDF in some way so that the memory usage isn't so high? I know I probably used the wrong application for such a basic need (since Livecycle comes with extra bells and whistles), so if anyone has a suggestion of a free/cheap alternative I'm open. Also, if more details are necessary please let me know.
Thanks!
Solved! Go to Solution.
Views
Replies
Total Likes
You must be running an older version of Designer. There was a bug where if you did a copy and paste (under certain conditions) a part of the XML was repeated over and over. Each time a copy/paste operation was performed this area woudl double in size. In your case it grew so big that it was taking up all of the memory. There was a service pack created that woudl "fix up" the file when it was opened in Designer. I did this and now your file is usable.
Please see the attached file.
Paul
Views
Replies
Total Likes
Bump - no ideas anybody?
Views
Replies
Total Likes
Would it be possible to post the form? I've had issues with forms I've imported from other programs in the past but it could be something as simple as a corrupt field somewhere in the form.
Yes, thanks. Attached is the PDF that seems to use a ton of memory.
Views
Replies
Total Likes
Hi agpierce,
The form is well laid out and subformed, but it looks to me like you could unwrap all but the uppermost subform with no trouble at all. Also, some of the headers are captions of fillable text fields rather than just regular text. Changing these should drop some weight and improve performance but to be honest I can't see anything wrong with the form. I'm going to experiment with it a bit and see if I can speed it up a bit.
I'll pare out the subforms then. I opted for those funky fillable text fields because the static text fields would occasionally blank out spontaneously, while the fillable fields wouldn't, but I'll get those replaced.
Thanks for your time.
Views
Replies
Total Likes
You must be running an older version of Designer. There was a bug where if you did a copy and paste (under certain conditions) a part of the XML was repeated over and over. Each time a copy/paste operation was performed this area woudl double in size. In your case it grew so big that it was taking up all of the memory. There was a service pack created that woudl "fix up" the file when it was opened in Designer. I did this and now your file is usable.
Please see the attached file.
Paul
Views
Replies
Total Likes
Goodness gracious, sure enough that file works like a charm! Thanks so much for your help folks!
Now I have to investigate this service pack.
Views
Replies
Total Likes
Paul,
At which version was this fixed? When I opened the original form agpierce posted I checked the version in the form properties, it's listed as 8.2.1... etc. I had experienced the same XML bloating you described in the past, but I thought it was fixed well before version 8.
Views
Replies
Total Likes
I am not 100% sure which service pack fixed it ...but I am running version 8.2.1 of Designer.
I found a link to a previous post that decribes this:
http://forums.adobe.com/message/1359052#1359052
Paul
Views
Replies
Total Likes
Its not the form ...its the version of Designer that is the issue. The problem exists in the XML source for the template which gets embedded in the PDF. Because of the compression in PDF the file gets really small and it then becomes difficult to spot. If you save the file as an XDP and the file is greater than 250K I would suspect that you have the issue.
Paul
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies