We used 23.7 version of the API and the following code snippet to test the scenario in our environment. We could not notice the OOM Exception. Can you please make sure that you are using the latest version? Also, please let us know about your complete environment details i.e. OS Name and Version, Application Type, RAM Size, etc.
It is also possible that the exception is being thrown due to other Aspose API that is being used. Please try to create a separate console application and test at your end using only Aspose.PDF and let us know in case you find any issues.
Aspose.Pdf.Document _document = new Aspose.Pdf.Document(dataDir + "1.pdf");
TiffSettings options = new TiffSettings();
//options.Compression = CompressionType.CCITT4;
Resolution resolutionObj = new Resolution(200);
options.Shape = ShapeType.None;
options.CoordinateType = PageCoordinateType.MediaBox;
options.Brightness = 0.5F;
TiffDevice tiffDevice = new TiffDevice(resolutionObj, options);
RenderingOptions RenderingOption = new RenderingOptions();
RenderingOption.IgnoreResourceFontErrors = true;
tiffDevice.RenderingOptions = RenderingOption;
using (FileStream imageStream = new FileStream(dataDir + DateTime.Now.Millisecond + @".tif", FileMode.Create))
{
tiffDevice.Process(_document, imageStream);
imageStream.Close();
}
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFNET-55267
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
You can check the issue status which is attached at the bottom of this thread. Apart from this, we will also keep you informed via this forum thread about issue progress and status.
Duration for the fix of the issue depends upon various factors. Please note that the issues in the free support model are resolved on a first come first serve basis. Resolution time of the issue depends upon the number of issues logged prior to it as well as nature and complexity of the issue itself. Furthermore, the issues in paid support are dealt with the highest priority and they have precedence over free support issues. In the paid support, immediate resolution of the issue is not guaranteed but investigation against the issue is performed quicker in order to provide fix ETA.
We are afraid that the earlier logged ticket has not been fully investigated yet. As soon as it is investigated, we will be able to share some updates about it fix or resolution ETA. Please be patient and spare us some time.
We are afraid that the earlier logged ticket has not been yet resolved due to other pending issues in the queue. Nevertheless, we have already recorded your concerns and will surely update you as soon as we make some progress towards ticket resolution. Please be patient and spare us some time.
Your concerns have already been recorded and we are afraid that we do not have any updates yet regarding ticket resolution. We will certainly inform you as soon as some news is available about issue fix. Please spare us some time.
Upgrading your license should not generally have any impact on the .NET Total APIs. Furthermore, we will let you know about the fix ETA for the logged ticket as soon as we complete the investigation.