goatcorp / XIVLauncher.Core

Cross-platform version of XIVLauncher, optimized for Steam Deck
GNU General Public License v3.0
84 stars 35 forks source link

Staying with settings open can crash the entire system #138

Open Kimikz opened 1 month ago

Kimikz commented 1 month ago

So, this is really curious but staying in xlcore settings for some minutes can cause a crash and if you try to relaunch more times all programs just close and the entire session is ununsable.

maybe gamemode implementation is causing this, disabling it with GameModeEnabled=false in launcher.ini and no crashes after almost an hour with settings open.

last-boot.log

interestings parts of this dmesg :

Mar 19 17:00:09 archie gamemoded[1708]: Adding game: 26328 [/opt/XIVLauncher/XIVLauncher.Core]

Mar 19 17:00:17 archie plasmashell[1424]: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No client registered with id '26328'")

Mar 19 17:00:17 archie plasmashell[26328]: dbus[26328]: arguments to dbus_pending_call_block() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 766.

Mar 19 17:00:17 archie plasmashell[26328]: This is normally a bug in some application using the D-Bus library.

then everything starts to fail.

Momorar commented 1 month ago

I can confirm that this has happened to me as well. I assumed it was a wayland quirk but attempted replication has shown that it occurs on x11 as well. Launcher crashes after about 3-4 minutes and when relaunched causes the entire sessions to die. With gamemode disabled, no such crash occurred after tens of minutes of idling in both wayland and x11.

red-star-fighter commented 1 month ago

Happening to me as well. I'm the one who sent Kimikz the last-boot.log file. Just turned off gamemode and not only does the app seem to not crash, this fixed some huge lag happening when in the settings panel.

EtereosDawn commented 12 hours ago

the same occurs in fedora 40 worksation