What steps will reproduce the problem?
Using the PdfWrapper class from C# will result in severe memory usage when
repeatedly rendering the PDF. I am using .NET 4.0.
Specifically:
I found that:
1) when using mupdf the mupdfEngine is not deleted (result: pdf file cannot be
deleted until application is closed)
2) destructor from AFPDFDoc never called due to missing cast
Find attached a SVN patch that fixes those problems. It also fixes a duplicated
call of Dispose() of PdfWrapper (which never showed up due to the first two
problems).
I also attached a very slim test program (that is only Form1.cs of it; just
create a form with a PictureBox and 4 Buttons using default names VisualStudio
assigns)
And finally there is a "patch" which creates a fine PdfLibNet.dll for .NET 4.0
Original issue reported on code.google.com by notdiffi...@gmx.net on 22 Jan 2011 at 10:03
Original issue reported on code.google.com by
notdiffi...@gmx.net
on 22 Jan 2011 at 10:03Attachments: