-
Notifications
You must be signed in to change notification settings - Fork 176
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.
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
Ferdium crash after update v6.7.4-nightly.10 #1758
Comments
please try running from the terminal (just guessing if that can show some logs). |
Thanks
|
Rollback to |
Try backing up your config, then re-opening the app. In my case the problem appears while maximizing the window. Since by default the app opens in a non-maximized way, it started ok with clean config. As soon as I've tried to maximize it, it crashed. Hope it helps |
Might be related to the issues here: https://github.com/electron/electron/issues?q=is%3Aissue+is%3Aopen+crash+on+startup+maximized |
Thanks, its work fine when i stay on the minimize windows but after full windows, its crash |
Please try with the latest nightly (11) since I have downgraded the electron version. |
Fixed in latest version of electron in this PR. Will be released in the next nightly approx 20 hrs |
Nightly.11 works - it now longer crashes on Linux - however it's now indefinitely using a large amount of CPU (process: /tmp/.mount_FediuEVIOpx/ferdium). |
Thanks, Work fine for me without to use than memory for me |
Avoid duplicates
Ferdium Version
6.7.4-nightly.10
What Operating System are you using?
Ubuntu
Operating System Version
Ubuntu 22.04.4 LTS
What arch are you using?
x64
Last Known Working Ferdium version
6.7.4-nightly.9
Expected Behavior
Just run Ferdium App
Actual Behavior
After update with Ferdium App, its impossible to run Ferdium. The windows appear and to close directly
Steps to reproduce
Debug link
No response
Screenshots
Additional information
I try with AppImage and .deb its same problem.
I will return to 6.7.4-nightly.9 and its work fine
Thanks
The text was updated successfully, but these errors were encountered: