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

Linux CPU usage at ~5% for blinking the cursor #148

Closed
krille-chan opened this issue Jul 15, 2023 · 2 comments
Closed

Linux CPU usage at ~5% for blinking the cursor #148

krille-chan opened this issue Jul 15, 2023 · 2 comments
Labels
stale The item is going to be closed soon because of inactivity

Comments

@krille-chan
Copy link
Owner

Description

Being a new user, I was checking out FluffyChat behavior, and noticed that it was constantly using 2-8% CPU, according to top(1). The only thing "moving" was the chat text cursor blinking. I'm curious if it can be optimized to save battery, or if this is an unavoidable side-effect of Flutter's rendering pipeline.

Note that the CPU usage is high even when my window manager has unmapped the window because it's on another workspace.

To Reproduce

  1. Start FluffyChat. Open a chat so the input text box is shown.
  2. Focus the input text box so the cursor starts blinking.
  3. Check CPU usage. It is 5%.
  4. Click anywhere else so the text cursor disappears.
  5. Check CPU usage. It is zero.

Additional information:

  • Device: Thinkpad T460s. Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
  • OS and OS version: Ubuntu 20.04, with the i3 window manager
  • Installed version of FluffyChat: From Snapcraft: v0.34.0+git559.5021d70b-dirty
Copy link

github-actions bot commented Mar 6, 2024

This issue is stale because it has been open for 120 days with no activity.

@github-actions github-actions bot added the stale The item is going to be closed soon because of inactivity label Mar 6, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The item is going to be closed soon because of inactivity
Projects
None yet
Development

No branches or pull requests

1 participant