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

Memory leak? #216

Open
vadi2 opened this issue Mar 14, 2023 · 9 comments
Open

Memory leak? #216

vadi2 opened this issue Mar 14, 2023 · 9 comments

Comments

@vadi2
Copy link

vadi2 commented Mar 14, 2023

The extension is using 2.7gb of memory, is this intended?

image

@RevAngel7
Copy link

I second this issue. After 24 hours my "cpufreq-service" uses 441 MB RAM and used up over 31:32.98 CPU time (avg. 0,11 CPU of a 6 core 12 thread CPU), and therefore is the 3rd most CPU using thread in the whole list, after the gnome-shell and Xwayland (on ubuntu 22.04). A system reset fixes that. CPU-temp goes down to 28 C from 34 C again.

@RevAngel7
Copy link

Bildschirmfoto vom 2023-04-03 09-46-16

@RevAngel7
Copy link

After a system restart it looks like this:
Bildschirmfoto vom 2023-04-03 10-04-00

@RevAngel7
Copy link

Alternative to a system restart you can kill the process "cpufreq-service" and then disable and re-enable the extension cpufreq to restart the service again. But it is definitely a memory leak which also uses up CPU power.

@RevAngel7
Copy link

Nothing happened for one month. And that issue eats away any systems RAM and CPU cycles. So a de-install then. Highly recommended, I mean, the de-install.

@vadi2
Copy link
Author

vadi2 commented May 3, 2023

As the person who filed this issue: that kind of attitude is not helpful to open-source maintainers. This tool is offered to you for free; if you don't like it, you can uninstall it yourself and not spread negativity around because your problem hasn't been addressed.

@RevAngel7
Copy link

OK, you are certainly right, @vadi2 . I am sorry and apologize for spreading my frustration.

@RobTheBuilder2
Copy link

Chiming in with a +1. I had to kill the process three days ago after it grew to 5.76G. Will keep an eye on it and happy to provide logs, etc that would help diagnose the issue.

@RobTheBuilder2
Copy link

RobTheBuilder2 commented Jun 20, 2023

Been running for 4 days. I'm now at 4.42G of mem usage. Let me know if I can provide logs or anything else that might be useful. I will have to kill it soon to prevent system issues but will keep capturing data post restart.

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

3 participants