[Bug]: Hyprland Becomes Unusable ( extreme lag) and Waybar Segfaults

[MostlyKIGuess]

Bug Report

Description

• So this happened after I updated my Arch from the past week, I thought it was maybe that or Hyprland not sure what exactly is causing this, but after like some time around 1-2 hours on runtime laptop cursor becomes unstable like just not usable, it just lags so much that to move from left to right of the screen it will take around 40-50 seconds.
• Now at first I didn't know why this was happening along with waybar getting segfaulted randomly, they aren't always together btw, they both can happen individually.
• So after I just reboot and it's fine , but today I noticed something while it was happening I saw the number of workspace going to 41 42 43 and closing it self which was weird and that's where the lag started to happen.

Steps to Reproduce

1.Not sure , it just happens randomly.

Expected Behavior

• Just not lag and stay stable?

Actual Behavior

• Lags and waybar getting segfaulted.

Screenshots

• it's so laggy I can't take a screenshot, nor that it would help.

Environment

• Linux Distro: ArchLinux
• Linux Version, output of uname -a: Linux mostlyk 6.13.5-arch1-1 Symlinks #1 SMP PREEMPT_DYNAMIC Thu, 27 Feb 2025 18:09:44 +0000 x86_64 GNU/Linux
• Hyprland Version, output of hyprctl version:
  ❯ hyprctl version
  Hyprland 0.47.2 built from branch at commit 882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff (version: bump to 0.47.2).
  Date: Sun Feb 2 00:47:17 2025
  Tag: v0.47.2, commits: 5767
  built against:
  aquamarine 0.7.2
  hyprlang 0.6.0
  hyprutils 0.5.0
  hyprcursor 0.1.11
  hyprgraphics 0.1.2

no flags were set

• Installation Environment: Main Hardware, Asus TUF A15
• Other info: using preferred, auto , 1 idk if that's useful.

Additional Information

• Will edit this once I get the segfault error from waybar.
• EDITED:
• Error logs of waybar:

❯ waybar
[2025-03-10 14:31:33.632] [info] Using configuration file /home/mostlyk/.config/waybar/config.jsonc
[2025-03-10 14:31:33.636] [info] Discovered appearance 'dark'
[2025-03-10 14:31:33.636] [info] Using CSS file /home/mostlyk/.config/waybar/style.css
[2025-03-10 14:31:33.647] [info] Hyprland IPC starting
[2025-03-10 14:31:33.649] [info] Loading persistent workspaces from Waybar config
[2025-03-10 14:31:33.649] [info] Loading persistent workspaces from Hyprland workspace rules

** (waybar:20927): WARNING **: 14:31:33.819: Status Notifier Item with bus name ':1.16' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
[2025-03-10 14:31:33.823] [warning] Requested height: 31 is less than the minimum height: 32 required by the modules
[2025-03-10 14:31:33.823] [info] Bar configured (width: 1920, height: 32) for output: eDP-1

** (waybar:20927): WARNING **: 14:31:35.561: Status Notifier Item with bus name ':1.16' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
[2025-03-10 15:06:02.587] [info] Loading persistent workspaces from Waybar config
[2025-03-10 15:06:02.587] [info] Loading persistent workspaces from Hyprland workspace rules
[2025-03-10 15:06:02.768] [info] Bar removed from output: grimblastVD

** (waybar:20927): ERROR **: 15:06:02.999: 
unhandled exception (type std::exception) in signal handler:
what: Invalid argument

wc: write error
[1]    20927 trace trap (core dumped)  waybar

[kRHYME7]

Check btop for something that might be causing this like eating CPU usage of ram.

[MostlyKIGuess]

Check btop for something that might be causing this like eating CPU usage of ram.

Yes I tried this when it happened, nothing unusual on htop, it's barely consuming 40-50% of the ram, load is around , all the cores are balanced.

[kRHYME7]

toggle gamemode.sh ? this disables animations and some eyecandy rendering. If this doesn't work and nothing is weird in the process list, try hyprland-git and see if they fix such issues already.

[MostlyKIGuess]

toggle gamemode.sh ? this disables animations and some eyecandy rendering. If this doesn't work and nothing is weird in the process list, try hyprland-git and see if they fix such issues already.

Right , I will update if it happens? in this issue and there as well if continues.

Thanks for the quick updates!

[MostlyKIGuess]

Update on waybar error:

❯ waybar
[2025-03-10 14:31:33.632] [info] Using configuration file /home/mostlyk/.config/waybar/config.jsonc
[2025-03-10 14:31:33.636] [info] Discovered appearance 'dark'
[2025-03-10 14:31:33.636] [info] Using CSS file /home/mostlyk/.config/waybar/style.css
[2025-03-10 14:31:33.647] [info] Hyprland IPC starting
[2025-03-10 14:31:33.649] [info] Loading persistent workspaces from Waybar config
[2025-03-10 14:31:33.649] [info] Loading persistent workspaces from Hyprland workspace rules

** (waybar:20927): WARNING **: 14:31:33.819: Status Notifier Item with bus name ':1.16' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
[2025-03-10 14:31:33.823] [warning] Requested height: 31 is less than the minimum height: 32 required by the modules
[2025-03-10 14:31:33.823] [info] Bar configured (width: 1920, height: 32) for output: eDP-1

** (waybar:20927): WARNING **: 14:31:35.561: Status Notifier Item with bus name ':1.16' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
[2025-03-10 15:06:02.587] [info] Loading persistent workspaces from Waybar config
[2025-03-10 15:06:02.587] [info] Loading persistent workspaces from Hyprland workspace rules
[2025-03-10 15:06:02.768] [info] Bar removed from output: grimblastVD

** (waybar:20927): ERROR **: 15:06:02.999: 
unhandled exception (type std::exception) in signal handler:
what: Invalid argument

wc: write error
[1]    20927 trace trap (core dumped)  waybar

[MostlyKIGuess]

Temp Fix Discussed on Alexays/Waybar#3974

[kRHYME7]

@MostlyKIGuess did it work? I don't remember we are using wireplumber though, I do remember we are using pulseaudio module.

[boulder-roller]

yipee its probably not my fault!

[RobertMueller2]

Temp Fix Discussed on Alexays/Waybar#3974

I'm fairly sure that is unrelated to the error above.