I was using Galaxy 2.0 today and happened to have process lasso open and noticed that while idle it was using 10-17% cpu while steam at idle was using .3%-1%. The client had already updated and imported after having been open for a few minutes.

I noticed high CPU usage yesterday, but right now the client is idling in the tray and the usage is not even reaching 1%.

For me the high CPU usage was right after installing and syncing all the libraries. After that I was playing around with the client, so maybe that was the cause. But since then everything seems fine when it comes to using hardware resources.

Yes this was well after I had opened the program, let it update any games and reconnect to the other services.

It was specifically a number of processes called "python.exe [32]" that are only active and running when Galaxy 2.0 is.

So probably something to do with account plugins, as those are written using python?

I forced the process that was using 10% cpu at idle to close and it crashed the Epic Games Store plugin within the client. It's reproducible so I went ahead and submitted a bug report through the client with attached logs and a screenshot of the failed integration in the client settings. I'm going to disconnect EGS from my client and watch Process Lasso for awhile to see if that solves the high cpu at idle problem.

Just to follow up I've been playing around with Galaxy 2.0 all day after disconnecting EGS and have not noticed any of the high CPU usage while idle at all. I left it sitting, I used it to play a game, took screenshots and then booted back down. Several instances of the python process would pop up, consume 1% cpu and then vanish without sitting at 10-12% usage like before.