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

Gnome 42.5 - Laggy UI when Argos enabled #147

Open
Naahuel opened this issue Apr 12, 2023 · 1 comment
Open

Gnome 42.5 - Laggy UI when Argos enabled #147

Naahuel opened this issue Apr 12, 2023 · 1 comment

Comments

@Naahuel
Copy link

Naahuel commented Apr 12, 2023

I'm experiencing a very laggy UI when Argos is enabled. Everything seems to freeze while the scripts are running (for example every 1s).

I started noting this while moving my mouse or moving windows. It's very clear on a website like this, with a constant animation
https://codepen.io/hexagoncircle/full/povGMod

Every 1s it freezes breefly. If I change the duration of the scripts to 2s, it does it every 2s. It even affects video (YouTube, or movies played with mpv).

Disabling Argos fixes the issue immediately. I've disabled every extension except for Argos and the problem persists.

A few people seem to have experienced something similar in this PR
#134

The Gnome Shell log doesn't seem to be logging anything of relevance, at least not every 1s.

You can kinda see it here, but it doesn't show very well in the screen recording.
Screencast from 11-04-23 21:10:05.webm

This is an (almost) fresh install of Pop OS 22.04 with Gnome Shell 42.5

Please let me know what I can do to help 🙏

@mwilck
Copy link
Collaborator

mwilck commented Sep 22, 2023

This is probably not an issue with argos itself, but with the scripts it is running. Argos is a very simple software, it just starts some programs in certain time intervals and displays the result.

You should figure out which of your scripts is causing the load. You could disable all argos scripts, enable them one by one, and see when the lag issue starts occuring. Next you can try to increase the time interval in which the offending scripts are run.

If this doesn't help, run "top" or something similar to figure out which processes hog the CPU.

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

2 participants