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

[BUG] High CPU use (Win 11 "High impact") #1386

Open
4 tasks done
Ander3232 opened this issue Dec 5, 2024 · 2 comments
Open
4 tasks done

[BUG] High CPU use (Win 11 "High impact") #1386

Ander3232 opened this issue Dec 5, 2024 · 2 comments
Assignees
Labels
bug Something isn't working triage This hasn't been chcked yet by any maintainer

Comments

@Ander3232
Copy link

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions.
  • This issue is about a bug (if it is not, please use the correct template).

Describe your issue

ElevenClock 4.4.1.1 uses 1% of my (fast) CPU. Under "Startup apps", Windows 11 calls it a "high impact" app.

Steps to reproduce the issue

Run the app

ElevenClock Log

(I copied the log and tried to paste it here, but the form said "Comment too long")

Relevant information

No response

Screenshots and videos

No response

@Ander3232 Ander3232 added bug Something isn't working triage This hasn't been chcked yet by any maintainer labels Dec 5, 2024
@marticliment
Copy link
Owner

I will investigate

@Carnbroe
Copy link

Carnbroe commented Dec 14, 2024

The increase in cpu happened in release just after version 4.3.3. Since then Elevenclock is now always the second item in the Task Manager details screen after the system idle process when the pc is at rest i.e. with no apps running. The current position , as indicated in the bug notification is that with the latest version 4.4.4.1 running under Win 11, the apps is now listed as high impact and sits with a solid 1% of CPU. I've now ditched Win 10 on my home PC but its the same issue there and was reported as bug #1365 As such Ive reverted back to 4.3.3 on my new Win 11 pc and turned off the auto update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This hasn't been chcked yet by any maintainer
Projects
None yet
Development

No branches or pull requests

3 participants