Flow Launcher Crashes: Capture a Minimal Reproduction
A useful crash diagnosis identifies the action that causes Flow Launcher to exit or show an exception. Preserve your configuration, record the exact error, and separate plugin, theme, and base-app behavior. Reinstalling immediately can remove the evidence needed to find the cause.
Steps to follow
- Write down the exact sequence before the crash, including the query and source plugin when known.
- Record Flow version, Windows build, and recent changes such as a plugin update or theme import.
- Back up UserData and reproduce with the implicated plugin disabled or with a built-in theme, changing only one factor at a time.
- Follow the project issue template or the plugin maintainer’s reporting instructions with a minimal non-sensitive example.
Check the result
The crash can be reproduced with a short sequence, or you have isolated the recent component change that triggers it.
Limits and common pitfalls
Logs and exception text can reveal private paths and query data. Redact secrets while preserving the meaningful error type and stack information.
Make the check repeatable
A minimal reproduction is not the same as a full copy of your workstation. Use a harmless filename, a temporary folder, and a basic query where possible. Keep the original profile available so you can confirm whether a proposed fix resolves the same symptom rather than a different configuration.
Questions and answers
Should plugin crashes be reported to the Flow project?
Start with the component identified by the error. The project support guide notes that third-party plugin issues may belong in the plugin’s repository.
Sources and scope
Related guides
Flow Launcher Slow Search: Isolate the Delayed Component
To diagnose slow Flow Launcher searches, compare local app results, indexed filenames, and network-backed plugins separately. The delay may be in an index.
Flow Launcher High Memory Usage: Compare Configurations
Investigate Flow Launcher memory usage by comparing idle behavior, repeated queries, and enabled plugins over a consistent period. One Task Manager.
Flow Launcher Settings Not Saving: Locate the Active Profile
When settings seem not to save, first confirm that you are reopening the same Flow instance and active UserData folder. Then check write access, duplicate.