ungoogled-chromium: Crash when a PDF tab is open
OS/Platform
macOS
Installed
Compiled from source
Version
121.0.6167.85
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
- I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using
--user-data-dircommand line argument and it could not be reproduced there
Description
Whenever I have a tab with a PDF file, the app crashes.
How to Reproduce?
- Open a normal ungoogled-chromium window with multiple tabs (Gmail, Wikipedia, etc)
- Open a new tab with a PDF file ( I am currently reading this book -> https://dn790008.ca.archive.org/0/items/TheElementsOfComputingSystems_201408/The Elements of Computing Systems.pdf)
- Open an incognito window with any other page (I open YouTube for music)
- Use the computer normally but eventually allow the computer to sleep with the PDF file tab open (As if you were reading the PDF file and decided to take a break with the PDF tab on the screen)
- When I log back in, ungoogled-chromium crashes (It might not crash on the very first try, but it crashes on the 2nd or 3rd)
Actual behaviour
If I have multiple tabs open on both normal and incognito windows, and I have a tab with a PDF file and allow the computer to go to sleep (auto-lock) on the PDF tab, when I log back in ungoogled-chromium crashes.
Screenshots:
It has happened multiple times, and I can’t understand why.
Expected behaviour
It shouldn’t crash.
Relevant log output
No response
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 20 (11 by maintainers)
I have the PDF opened… You can send the crash report (it usually doesn’t contain any sensitive info), but I doubt if it will really help in our case (where we basically just add patches to another software).
By the way, @k-afonso can you update to the latest version of Ungoogled Chromium just to make sure this situation still exists? And please send a more detailed information (Mac Model, macOS version) about your device.
The bug seems to be fixed in the most recent version 122.0.6261.111-1. If anyone experiences the same (or a similar) bug, try updating to the most recent version available.
@PF4Public Hi, I tried reproducing the bug several times and I couldn’t. I guess it’s fixed in this later version. Thank you guys for your great help!
@k-afonso Have you tried any later version? Perhaps it’s fixed there.
Yeah I can say it’s not very useful…
I’ll try to duplicate it again and if it’s still not working then I don’t know what can we do in a short term…
It might even be a device specific issue, which will be hard to diagnose.
I am testing on an ARM machine
Sadly I can’t duplicate this issue on my side following these steps:
Sorry I was in a rush, I haven’t experienced anything like this, but I will try to reproduce this later this week just following these instructions.