Your problem may well be unrelated, this is just something to look for and try to see if it gives any improvement. Other services may not restart so safely or cleanly, and can break things if poked in the wrong way. It can clear the high memory usage for a while, and possibly other transient issues. This will kinda break Aura briefly, but it should recover automatically and put the lights back to their last configured mode within a minute or so.Īs I said, I don't recommend restarting services randomly or carelessly, but it seems to work ok for LightingService. To restart LightingService and temporarily clear the excessive memory usage, do the following:
#Logitech gaming software memory leak full
Don't go around restarting other services unnecessarily or carelessly, and don't change the startup options without knowing what each service actually does (the descriptions don't tell the full story in some cases). This is not something to do with services in general, but it seems safe enough for LightingService. There's really no legitimate reason for it to be growing into the 100s of MB or past 1GB over time. After a restart of the service, it starts out around 12MB for me, grows to about 20MB fairly quickly, then steadily grows seemingly without limit. On systems with less memory, that leak is likely to result in poor performance after it has been running for a while, due to its pages getting pushed out to swap. It's leaking over 1GB RAM per day for me, although the latest version has solved a slowdown I was personally encountering that seemed to go along with the leak. I suspect there's something else going on here, but it's possible that you could be getting poor performance due to the fairly bad memory leak in LightingService.exe (particularly if you have "Aura Performance Mode" enabled for smoother lighting animation).
0 kommentar(er)
