Skip to content
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

GogDL not working and using all memory (leak) #46

Open
ImLaZyBear opened this issue May 28, 2024 · 3 comments
Open

GogDL not working and using all memory (leak) #46

ImLaZyBear opened this issue May 28, 2024 · 3 comments

Comments

@ImLaZyBear
Copy link

Hello,
I have a pending update for The Witcher 3 on GOG.
The updates starts and 3 processes of gogdl are spun up.
They are slowly taking all my ram and the progress is not moving forward. Very low network activity like 5kbps max
CPU usage and RAM usage increasing without stopping.
Had to kill the processes because my ram was full and it was going to use all my SWAP.

Here are the logs of GOG :
gog.log

@3vilg3nius
Copy link

Currently having the same issue with an update for Diablo on GOG, exact same symptoms.

@error161
Copy link

error161 commented Dec 6, 2024

Same issue here too, also was a Diablo GOG update that kept trying to repeat itself and failing so I attempted to uninstall and reinstall after messing with the download a few times. Memory completely filled and system was unusable, could not get to a terminal or any other means of getting it under control. After restart of the system, it appears the reinstall was successful and things are back to normal.

On the same version, in days past, updates have been working fine, so not sure why today is the first time something odd has happened like that with an update. Curious to see if the issue begins to repeat with any other updates that get triggered.

@maste9
Copy link

maste9 commented Jan 10, 2025

There are a lot of people experiencing that problem: Heroic-Games-Launcher/HeroicGamesLauncher#3695

If I stop the Download and even HGL then ps aux | grep gogdl outputs a lot of gogdl processes which I have to kill by hand. Which might explain the growing memory leak?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants