[Bug]: 2.6.0 crashes as soon as you open a PDF file

[daniporr]

Installation Method

Local Installation

The Problem

1. Open any tool
2. Load a PDF
3. The app crashes, and the browser says: "Error code: STATUS_ILLEGAL_INSTRUCTION"

Version of Stirling-PDF

2.6.0

Last Working Version of Stirling-PDF

2.5.2

Page Where the Problem Occurred

Any page where you can open a PDF file

Docker Configuration

Relevant Log Output

Additional Information

I don't see any error in the logs nor in DevTools

Browsers Affected

Chrome

No Duplicate of the Issue

• I have verified that there are no existing issues raised related to my problem.

[dosubot]

This appears to be a known issue related to WebAssembly compatibility in Chromium browsers. A similar STATUS_ILLEGAL_INSTRUCTION error was reported in v2.5.3, originating from /pdfium/pdfium.wasm.

Key finding: The issue does not occur in fresh browser profiles, suggesting it's browser-profile-specific rather than an application bug.

Try these workarounds:

1. Open Stirling-PDF in an incognito/private window
2. Create a new Chrome profile and test there
3. If that works, clearing your main profile's site data for the Stirling-PDF domain may help

Standard cache clearing hasn't resolved the issue for others, so trying a fresh profile is the most reliable test. Let us know if the incognito window works for you!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[balazs-szucs]

Hi,

I think the last time someone reported something like it was because of security configuration. E.g., they had their browser on some "strict" security setting, which caused this. I'm afraid, I am not very familiar with Chrome can you check if there also such setting there and what happens if you turn the security setting down the minimum?

Thanks!

[daniporr]

Hi @balazs-szucs, you are right, disabling the security features resolved the issue!

Do you have any idea why this wasn't a problem in previous versions?
I had previously used version 1.x and have been using version 2.x until now, with the same browser and settings, without experiencing any issues.

Anyway, I believe we can close this issue now.
Thank you for your prompt assistance.

[Frooodle]

Will investigate this further and keep issue open for now
Hopefully we can resolve it so it works even with the flag

[daniporr]

It may be of interest to note that:

• on Firefox, even with the most stringent settings, it works perfectly.
• on Edge:
  • with 'Enhanced security' enabled, it doesn't work.
  • with 'Enhanced security' disabled, it works even with 'Tracking prevention' set to 'Strict'.