Bruno wrote:
> I hope you find the problem. I know from experience
> that these kind of problems are hard to solve...
I have solved this problem.
For those who are interested (I will be cross posting on the iTextSharp list
as well because this is a .NET problem):
It appears to be an issue with the .NET Garbage Collection and COM interop.
By adding
System.Runtime.InteropServices.Marshal.FinalReleaseComObject(comObj);
GC.Collect();
GC.WaitForPendingFinalizers();
during the Path painting loop I was able to complete the whole document
without exception.
The MS documentation warns that this forced GC collection has an impact and
it does; the processing time has gone from 30 minutes to about 3.5 hours but
the document is produced.
I had other problems once the document was produced. Reader(7) gave an
"Operation or data too complex" error so I optimised the document. Reader
then opened most of the layers and threw a "There is a problem reading this
document (18)" error. A Google search produced a quick result "Download
Reader 8". Which I did. The document can now be read.
Cheers
AlanK
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/
