We are experiencing a recurring issue when parsing PDF documents using Spire.PDF version 11.9.17.
We have attached one example PDF document that consistently produce the following error in our application:
**“Spire error loading from stream”**
This is currently the **most common Spire.PDF error** we are encountering. We have **thousands of PDF documents** that fail with this error, so we would like to understand what is causing it and whether there is a known issue or recommended workaround.
Environment
- Spire.PDF:** 11.9.17
Application:** Desktop Windows application
.NET:** .NET 10
Operating System:** Windows Server 2019
Execution environment:** Azure Windows VM
Azure region:** South Central US
Task:** PDF document parsing/loading from an Azure Storage stream
The error occurs when calling `LoadFromStream()`:
- Code: Select all
var pdf = new PdfDocument();
try
{
Retry.RetryAction(() => pdf.LoadFromStream(stream));
// pdf.LoadFromStream(stream);
}
catch
{
// spirePdfError = true;
throw new Exception("spire error loading from stream");
}
We are already using a retry mechanism around `LoadFromStream()`, but the documents continue to fail.
Could you please help us determine:
1. **What causes the “error loading from stream” error?**
2. Are there any known issues with **Spire.PDF 11.9.17** that could cause this behavior?
3. Could this be related to the **PDF structure/content** of these documents?
4. Are there specific PDF features, encoding, compression, encryption, malformed objects, or other characteristics that could trigger this error?
5. Is there a recommended way to validate or repair the PDF before passing it to `LoadFromStream()`?
6. Would upgrading to a newer version of Spire.PDF resolve any known issues related to loading PDFs from streams?
7. Is there anything specific we should check regarding the **Stream** itself (position, seekability, length, etc.) before calling `LoadFromStream()`?
We would also appreciate it if your team could review the attached PDF sample* and let us know what they have in common that might cause Spire.PDF to reject them.
Since we are seeing this issue with thousands of documents, identifying the underlying cause or a reliable workaround would be very helpful.
Thank you!
