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.

Sign up for GitHub

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

Jump to bottom

Performance issues under GNOME wayland #357

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

Performance issues under GNOME wayland #357

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

Comments

@krille-chan
Copy link
Owner

Description

Trying to use Fluffychat under GNOME/Wayland (I haven't tried xorg) has performance problems.
The mouse cursor is laggy and none of the animations are smooth. I can also see a spike in CPU usage every time I focus the fluffychat window!

The issue seems to be related to the size of the window. I have two 4k monitors that are powered by an eGPU. My guess would be that the application is for some reason bypassing the GPU and instead renders using the CPU? Not sure if that is a known Flutter issue.

As I decrease the size of the window, things begin to work smoothly!

To Reproduce

Install fluffychat and try to use it.

Additional information:

  • Device: Thinkpad t480
  • OS and OS version: Manjaro. Kernal version 5.10.109-1-MANJARO
  • Installed version of FluffyChat: 1.4.0
  • (Android only) Which store are you using:
  • (Android only) Are Google Services available:
@github-actions GitHub Actions
Copy link

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 Dec 27, 2023
@github-actions GitHub Actions
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 Jan 10, 2024
@basings basings mentioned this issue Jan 23, 2024
Closed
@Henry-Hiles Henry-Hiles mentioned this issue Feb 7, 2024
Closed
@Mart-Bogdan
Copy link

Lol. why is it closed? did performance become better?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale The item is going to be closed soon because of inactivity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mart-Bogdan @krille-chan