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

Consuming 99% CPU, restarts itself (must auth many times) #67

Open
spikespaz opened this issue May 13, 2024 · 1 comment
Open

Consuming 99% CPU, restarts itself (must auth many times) #67

spikespaz opened this issue May 13, 2024 · 1 comment

Comments

@spikespaz
Copy link

spikespaz commented May 13, 2024

Using Hyprland master, Nixpkgs nixos-unstable, also using #49. I have three monitors, middle, left, and top. Coordinates: middle (1920, 1440), left (0, 1440), top (1600, 0). Sizes and scaling: middle (2880, 1800, 1.5) virtual (1920, 1200), left (1920, 1080, 1.0), top (2560, 1440, 1.0).

With Factorio (Xwayland) open on the top monitor, I noticed the game stuttering. I check top, and see that swaylock is using >99% CPU. Killed the PID, then swaylock restarts. Factorio continues displaying animation frames while the other two screens are showing the lock screen as configured. I then had to authenticate several times because swaylock restarts itself after a successful authentication. Eventually, maybe 5 tries (has been more historically), it finally goes away and there is no more swaylock process.

Questions:

  1. What is going on with Factorio, why does it render above the lock screen surface?
  2. Why was there a zombie swaylock process using infinite cycles?
  3. Is Add fingerprint functionality via fprintd DBus service #49 malicious?
  4. Why did the process exit gracefully when I issued kill (TERM: 15) instead of kill -9 (KILL: 9)? Shouldn't it render the session useless if it is killed, and disallow TERM?
  5. Why did it restart itself many times?
  6. Are there several unrelated problems here?

The reason I ask all of these in a single issue is because all of these symptoms cropped up at the same time (considerable time after making #49 part of my setup I might add).

@spikespaz
Copy link
Author

This just in: swaylock started randomly, despite me playing a game (active HID input). This time, Factorio was covered by the surface. When I authenticated, the game's keyboard and mouse was unresponsive until I (1) focused another window, (2) resized that window, (3) resized Factorio. After this sequence, I can continue sending input events to Factorio.

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

1 participant