pdfium | Mirror from http : //pdfium.googlesource.com/

0x80131506 is Fatal Internal CLR error normally stemming from Interop and is not try/catchable.

The bug is caused by the use of an experimental .NET runtime .NET 5.07 and above currently have a known issue / breaking change with Interop.

.NET 5 latest does not have LTS Long Term Support and is a balance of bleeding edge technology over stability.

2 ways to fix it:

1. IronPdf now have a fix on their main branch: https://www.nuget.org/packages/IronPdf/

2. Target a more stable .NET run time ( .Net Core 5.0 or 3.1 LTS) .NET 6 will be an LTS. Until then .Net 3.1 has long term support and is stable. https://blog.inedo.com/dotnet/demystifying-lts

I was wrong thinking PdfiumCore is a binary provider package for PdfiumViewer. but it's an standalone package and as it uses a much newer Pdfium version (that seems to be a critical point for using pdfium) I decided to use it. (I also tested https://github.com/GowenGit/docnet and it worked fine but it use an older version of PDFium)

So used https://github.com/Dtronix/DtronixPdf/ (that is a thread safe implementation of PdfiumCore) and cleaned it to make a PDF To Image Converter from it and tested it on Windows and Linux. here's the final code: https://github.com/hmdhasani/DtronixPdf/blob/master/src/DtronixPdfBenchmark/Program.cs

I am not sure about why this is happening, but i resolve it by cleaning the flutter project. Thankyou

In my opinion Adobe Acrobat is right but the specification could be read differently, too.

Your PDF contains the following content stream:

FPDF_EXPORT and FPDF_CALLCONV are Macros, they are defined in the file : https://pdfium.googlesource.com/pdfium/+/master/public/fpdfview.h

They are needed here because the library is available for different systems, and different systems have different conventions for creating the library interface.

These calls are extensions to the format you are familiar with:

Check your threading and make sure there is no concurrency issue, as per doc it's not thread safe: https://developer.android.com/reference/android/graphics/pdf/PdfRenderer

This is how I'm loading pdf url:

fragment_pdf_reader.xml:

I don't think this is fixable, because the tool does nothing wrong. After investigation, the PDF writes out a real period, the instruction used is:

It seems that the Visual Studio debug runtime code has a section in the destructor of std::vector that assumes iterator debugging. I can't post the code here, due to probable copyright issues.

My guess is that the debug runtime expects the allocators to be stock Visual C++ allocators, with debugging information. Someone will correct me if I'm wrong, but this is where the static_assert is pointing to.

What you can do is build a Release mode only, since a release build does not invoke the debug library code.

However, if you desire to easily debug the application you can:

1) Set the iterator level to 0 (_ITERATOR_DEBUG_LEVEL preprocessor symbol should be 0) and rebuild

or

2) Create another configuration (call it Release With Debug) and copy the same settings for Release, except that the optimizations should be turned off.