-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
app won't close (trainer) and keeps running in the background #12
Comments
Could you provide me with the trainer name that you test with? I guess this issue also related to some specific trainers. |
I have been testing mainly with Hogwarts Legacy and Baldur's Gate 3 on my desktop, and Octopath Traveler on SteamDeck (with 10% CPU usage) when I tested Persona 4 Golden and Persona 5 Royal on SteamDeck they didnt have this issue, also noticed that Soul Hackers 2 didn't launch at all PS. one issue with AppImage version seems to stop working because of this, what I mean that you cant relaunch it when this happens also seems that the whole app is running in the background |
It should be a trainer related issue. Although I can't reproduce it, I will fix it by killing all processes before closing LaLa, as that would be safer.
It is also a trainer related issue. see:#4
Could you please provide more details, including the steps to reproduce and any error messages encountered? |
I notice that this seems to be a nvidia driver issue, I assume ...cant 100% confirm. but on my AMD laptop I dont have any these issues. about the AppImage thing, it has happened two times to me...not sure what causes it ....my guess is that its related to this background task issues |
Update: |
so I notice that trainers keeps running in the background even after I have closed the app, this happens on both flatpak and AppImage ...and for example if I opened the trainer on flatpak then closed the app then reopened the same trainer with Appimage it opened both version of the trainers...BUT the background process amount keep increasing (especially the .cache every time you launch a trainer, even if its the same trainer)
The text was updated successfully, but these errors were encountered: