Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Opening PDF documents in Chromium-based browsers causes a STATUS_STACK_OVERFLOW failure #18135

Closed
rodolfoorl opened this issue May 21, 2024 · 8 comments · May be fixed by #18151
Closed

Opening PDF documents in Chromium-based browsers causes a STATUS_STACK_OVERFLOW failure #18135

rodolfoorl opened this issue May 21, 2024 · 8 comments · May be fixed by #18151
Labels
performance

Comments

@rodolfoorl
Copy link

Attach (recommended) or Link to PDF file here:

  • For RGPD reasons I cannot send the document PDF

Configuration:

  • Web browser and its version:
    • Chromium-based: 125.0.6422.60 (Crash with STATUS_STACK_OVERFLOW)
    • Mozilla Firefox 126.0 (Slow and consumes a lot of CPU, but not crash)
  • Operating system and its version:
    • Windows Pro 11 Version: 10.0.22631 Build: 22631
  • PDF.js version:
    • v4.2.67
    • v3.11.174
    • v2.9.359
  • Is a browser extension: No

Steps to reproduce the problem:

  • I still don't know how to replicate the problem from another PDF.
  • Information I have and can provide:
    • This PDF was powered by Crystal Reports; modified using iText® 7.1.13 @ 2000-2020 iText Group NV (AGPL-version)
    • This PDF has been altered or corrupted since it was signed (Information obtained when I open it in Adobe Acrobat)

What is the expected behavior?

  • Open the specific document PDF file with pdf.js in a Chromium-based browser without causing a STATUS_STACK_OVERFLOW

What went wrong?

  • Case 1 - Using Chromium-based browser:
    In this case, I try to open the specific document in Chromium-based browsers (In the video I used the Brave browser, but the same problem occurred in Edge and Chorme) - And after a few seconds the browser crashes with STATUS_STACK_OVERFLOW
Chromium-based.browser.mp4
  • Case 2 - Using Mozilla Firefox browser:
    In this case, I try to open the specific document in the Mozilla Firefox browser, using the browser's own native pdf.js - It spends time consuming a lot of CPU and the entire browser interface slows down and freezes, but does not crash - The message is also displayed that this tab is slowing down the browser and asks me if I want to stop it.
Mozilla.Firefox.browser.mp4

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
@Snuffleupagus
Copy link
Collaborator

Attach (recommended) or Link to PDF file here:
* For RGPD reasons I cannot send the document PDF

Unfortunately the only way for this, or any other, issue to be actionable/valid is if you provide access to the PDF document since it's impossible to fix/improve something that cannot be reproduced.

@calixteman
Copy link
Contributor

Sorry but we aren't genius and we can't guess what's wrong with just a video showing a number.
You can file a bug for Firefox:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF%20Viewer
attach your pdf and check the box Confidential Mozilla employee:
image
or send it to me on my pro email (I'm the triage owner of the bug component from the link above)
And if it's too much confidential, sorry but as Snuffleupagus said, there is no way to fix your issue.

@rodolfoorl
Copy link
Author

Unfortunately the only way for this, or any other, issue to be actionable/valid is if you provide access to the PDF document since it's impossible to fix/improve something that cannot be reproduced.

I understand... I will check the possibility of sending a document with the same problem that does not contain sensitive information so that we do not have problems with GDPR on our part.

I will get back to you soon and thanks for the quick response.

@calixteman
Copy link
Contributor

Another possible solution is to record a profile in Firefox:
https://profiler.firefox.com/
And when you upload the profile take care to remove the screenshots in order to avoid to leak whatever informations.
It could be possible to guess what's wrong from the profile.

@rodolfoorl
Copy link
Author

rodolfoorl commented May 21, 2024 •
edited
Loading

Sorry but we aren't genius and we can't guess what's wrong with just a video showing a number. You can file a bug for Firefox: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF%20Viewer attach your pdf and check the box Confidential Mozilla employee: image or send it to me on my pro email (I'm the triage owner of the bug component from the link above) And if it's too much confidential, sorry but as Snuffleupagus said, there is no way to fix your issue.

I created the issue at bugzilla.mozilla.org with the Security-Sensitive Firefox Bug flag and sent the videos and documents that present the problem.
https://bugzilla.mozilla.org/show_bug.cgi?id=1898053

@calixteman
Copy link
Contributor

@rodolfoorl in the bug, could you change the product to Firefox and the component to PDF Viewer ? I don't have access to the bug (or you can cc me on the bug and I'll make the change).

@rodolfoorl
Copy link
Author

@rodolfoorl in the bug, could you change the product to Firefox and the component to PDF Viewer ? I don't have access to the bug (or you can cc me on the bug and I'll make the change).

Done!
image

@Snuffleupagus Snuffleupagus linked a pull request May 23, 2024 that will close this issue
Auto-close any open BMC/BDC when ending text (bug 1898053) #18151
Open
@Snuffleupagus
Copy link
Collaborator

Closing as duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1898053 (to avoid tracking the same issue in multiple places).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Auto-close any open BMC/BDC when ending text (bug 1898053) calixteman/pdf.js
4 participants
@timvandermeij @Snuffleupagus @calixteman @rodolfoorl