desktop: Zen reliably crashes on my laptop when I resume from suspend
Captchas
- I have read the instructions.
- I have searched existing issues and avoided creating duplicates.
- I am not filing an enhancement request.
What happened?
I have Zen Browser running fine on my laptop. I close the lid to suspend my laptop. I wait for it to go to sleep then open the lid to resume from shutdown. Zen crashes within a few seconds, or the first time I try to interact with its window.
Reproducible?
- I have checked that this issue cannot be reproduced on Mozilla Firefox.
Version
1.0.2-b.5
What platform are you seeing the problem on?
Linux
Relevant log output
I don't know where to look for logs, but when I run Zen from the terminal I see just the following output on resume:
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=34.0139) Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=34.498) Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
zsh: bus error (core dumped) ./browser/zen-x86_64.AppImage
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 18 (3 by maintainers)
This indeed looks like an AppImage issue. I’ve switched to the tar.bz2 version of 1.7.2b and didn’t have a single crash even though my laptop went to sleep many times.
However my application icon is now a Wayland icon instead. 👉 #3578 (Using KDE as DM, Gnome seems to be unaffected)
Is it only on the appimage version?
After following this, Zen has stayed open, after many times suspending and waking, without any crashes of the app or any tabs. Tabs and, eventually, the whole app, used to crash for me, but this seems to have fixed the problem on my system.