🐛 Loop immediately crashes when Next + Previous screen in a Cycle is triggered

[akincan-kilic]

Bug Description

When a Cycle is created with 2 Screen Switching components inside (Next and Previous), and that shortcut is triggered Loop will crash, leak memory.

Steps To Reproduce

1. Open Loop settings
2. Go to keybindings
3. Click + -> More -> Cycle
4. Click to edit the Cycle
5. Add Screen Switching -> Next Screen
6. Add Screen Switching -> Previous Screen
7. Name the Cycle "Screen Switching" and save it.
8. Assign any keyboard shortcut to it (Mine is ⌥ + ⌃ + ⇧ + Space)
9. Try the assigned keyboard shortcut.

Expected Behavior

Loop will show a preview of the window appearing on my other screen, and after repeating the shortcut make it appear on my first screen. Thus cycling between my two main monitors.

Actual Behavior

Loop immediately crashes, leaving a hollow circle that is fixed on screen. Not only Loop will become unresponsive but it will start taking up more and more memory as time passes, reaching to infinity before killing itself.

Screenshots

The Hollow Circle after crash

The Cycle details

The Cycle in the keybinds menu

My Loop Settings

General Settings

More Settings

MacOS Version

Sonoma 14.5

Loop Version

1.0.0-beta.15 (817)

Additional Context

I have a Macbook Pro M1 Pro 16" laptop as my secondary display and a main display MSI Optix G32CQ4 31.5" running at 2560x1440 resolution and 120HZ with BetterDisplay application running to scale it to HiDPI.

Final Checks

• My issue title is descriptive
• This is a single bug (multiple bugs should be reported individually)

[mrkai77]

Yes, actually, when a screen switching action is added into a cycling window action, it will also automatically advance onto the next action (it assumes that the next action is a window resize). You can see this in action in the built-in actions in Loop. What is happening in your case is that it is looping through the cycling actions infinitely 😓

I would recommend adding a "buffer" non-screen-switching action in between them for now, but I will definitely try and fix this by the next release!