BUG: flow settings window freezes on multi-monitor

[zacharykai]

Checks

• [X] I have checked that this issue has not already been reported.

• [X] I am using the latest version of Flow Launcher.

Problem Description

The settings page often freezes and doesn't resize when I move it to another screen or full-screen it or make it smaller.

To Reproduce

1. Open the settings in the app.
2. Move the window to a new screen or try to resize it.
3. It freezes/slows down the computer.

Screenshots

No response

Flow Launcher Version

1.19.1

Windows Build Number

22631.4112

Error Log

Replace this line with the important log contents.

[Kylotan]

Same here. Task Manager reports that the Settings entry under Flow.Launcher.exe is using a full CPU core, and Process Monitor suggests that the program is - in my case, at least - continually reading Nvidia-related directories:

• C:\ProgramData\NVIDIA Corporation\Drs
• C:\ProgramData\NVIDIA Corporation\ShadowPlay
• C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d3828c822366e497\NvCamera\

Between reading those repeatedly, it is looking for and failing to find these .dlls (as they do not exist in that location, or anywhere on my machine):

\AppData\Local\FlowLauncher\app-1.19.1\aurora.dll \AppData\Local\FlowLauncher\app-1.19.1\jengined.dll \AppData\Local\FlowLauncher\app-1.19.1\rendspt.dll \AppData\Local\FlowLauncher\app-1.19.1\oculusmedium.exe \AppData\Local\FlowLauncher\app-1.19.1\petromod_nvidia_profile_identifier.ogl \AppData\Local\FlowLauncher\app-1.19.1\jengine.dll

This process seems to go on indefinitely (e.g. an infinite loop) with very gradual memory increases, most likely just memory fragmentation rather than a sign of it making any progress with an operation.

[jjw24]

hmm so far unable to reproduce on a single display, tried resizing + maximizing settings window.

[Kylotan]

Dual monitor here, for what it's worth, and still happens under 1.19.2. Looking for the exact same DLLs as above but now under the 1.19.2 directory, The sidebar of the settings populates but the main pane on the right stays blank.

It's worth mentioning that this doesn't happen every time. Like the other bug I've found with Flow Launcher (stopping responding to the hotkey), it seems to be something that doesn't happen immediately but is triggered after some time or by something changing in the environment.

[ghost]

Yes, the issue appears to exclusively happen for me on my computer with two extra monitors. The other without the extra screens doesn't have this bug.

[j-a-s-o-n-g]

I can say the same happens on my machine. It happens very frequently, but not immediately after restarting FL. For example, I'll be doing normal computer things for several hours after last pseudo-crash, right click tray -> settings and the left will populate, the right side won't. The entire window will not be interactable (but not "not responding"). I alt+f4 to force close it, but then the tray isn't interactive. No context window on right click. I either have to force quit the program or use the in-app "Restart Flow launcher" command.

Edition Windows 11 Home Version 23H2 OS build 22631.4169 Experience Windows Feature Experience Pack 1000.22700.1034.0

FL: 1.19.2

2 monitor setup.

Error logs do not contain any errors.

[Kylotan]

I found an easy repro case - on a multi-monitor setup, open Flow Launcher, and open the Settings window. Then drag it to the other monitor - it then stops processing window events and CPU usage goes up, as if in an infinite loop. Even dragging it around the screen starts to be laggy. Dragging it back to the original monitor restores normal operation.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

[github-actions[bot]]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

[jjw24]

Potentially fixed with 1.19.5, let me know if not the case I will reopen.