Hi Folks,
We have been using Arbortext as a publishing tool for almost a year now. So far we have not had too many issues we haven't been able to overcome. Typically our documents are between 50 - 200 rendered pages and contain images, lists, cross references, and often many tables.
From time to time, I get complaints from users indicating that after rendering documents multiple times, they get segment violations and Arbortext closes. The work around is to restart and keep going.
It seems that the more complex the tables get (cell spanning) the more likely we have issues. For fun, I took a document and copied the content many times over to see what would happen when we have a larger document - the result is Arbortext will just crash about 330 pages or so into rendering. From a system perspective, I can see memory usage climb (x32 version here) to just over 1.1 GB before the crash. The error I commonly see is editor.exe: segment violation (signal 11).
My question is this, how do others handle these issues and are there other settings under the covers that will allow Arbortext more memory or to process larger files? I am a bit nervous that someday soon we may run into a 600 page document that cannot be handled.
I looked into some of the stylesheet profiling tools - but again with the error message I am seeing - it doesn't tell me what is really happeneing. For reference we are using the APP engine and have a custom schema/stylesheet.
Any advise is welcome.
Thanks,
Rob.
