You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the past 3 weeks or so, MB has been crashing randomly on me. Happens on various websites and after various durations, can't isolate a pattern or obvious cause.
This has happened both while watching YT, as well as when doing general browsing or scrolling without YT at all.
Has happened as quickly as 3 mins, might be as long as after 2 hours of general browsing.
Any advice on how to troubleshoot? Frankly not even sure if its a MB specific issue, but it only happens to MB, FF works as expected.
Does MB capture any crash logs? Could I manually enable it for now?
I'm on the direct download version of MB
MB 13.5.2 (based on Mozilla Firefox 115.14.0esr)
Linux Fedora 40, KDE, Nvidia 560 drivers.
The text was updated successfully, but these errors were encountered:
Issue is still ongoing, finally managed to capture some logs from journalctl
systemd[14621]: Started app-Mullvad\x20Browser\x28Wayland\[email protected] - Mullvad Browser Setup - Web Browser.
rtkit-daemon[962]: Successfully made thread 16911 of process 16804 (/home/XX/mullvad-browser/Browser/mullvadbrowser.real) owned by '5555' RT at priority 10.
kwin_wayland_wrapper[14703]: error in client communication (pid 16804)
systemd[14621]: app-Mullvad\x20Browser\x28Wayland\[email protected]: Consumed 1min 16.932s CPU time, 2.2M memory peak, 0B memory swap peak.
I was doing general surfing, 2-3 tabs open, nothing intensive, no media playing, yet it crashed in just over a min.
Would appreciate any input to help debug this further, especially the kwin_wayland_wrapper line
Over the past 3 weeks or so, MB has been crashing randomly on me. Happens on various websites and after various durations, can't isolate a pattern or obvious cause.
This has happened both while watching YT, as well as when doing general browsing or scrolling without YT at all.
Has happened as quickly as 3 mins, might be as long as after 2 hours of general browsing.
Any advice on how to troubleshoot? Frankly not even sure if its a MB specific issue, but it only happens to MB, FF works as expected.
Does MB capture any crash logs? Could I manually enable it for now?
I'm on the direct download version of MB
MB 13.5.2 (based on Mozilla Firefox 115.14.0esr)
Linux Fedora 40, KDE, Nvidia 560 drivers.
The text was updated successfully, but these errors were encountered: