fff.nvim crashes neovim when opened from home directory

[umibear]

Opening neovim directly from home directory causes immediate crash. This is a hard crash — neovim exits completely.

In logs i can see

ERROR fff_search::file_picker: Refusing to index home directory: /home/user
ERROR fff_nvim::error: string_value="Can not run certain FFF features in a file system root or home directories. Consider smaller per-project directories."

=== CRASH SIGSEGV ===
signal 11
0:
1:
=== CRASH END SIGSEGV ===

Steps to Reproduce

1. Open a terminal in your home directory (cd ~)
2. Run nvim .zshrc (or any file in ~)
3. Neovim crashes immediately

Health command from neovim inside my dotfiles as i cant run that in home.
fff.nvim ~

• ✅ OK Binary loaded successfully from: /home/user/.local/share/nvim/lazy/fff.nvim/lua/../target/release/libfff_nvim.so
• ✅ OK fff.nvim version: 0.9.0
• ✅ OK libgit2 available (version: 1.9.2)
• ✅ OK Git repository found: /home/user/.dotfiles/
• ✅ OK File picker initialized (ready, 299 files indexed, base: /home/user/.dotfiles)
• ✅ OK Frecency database operational (76 entries, 52.0 KB, path: /home/user/.cache/nvim/fff_nvim)
• ✅ OK Query cache database operational (8 query-file mappings, 4 history entries, 60.0 KB, path: /home/user/.local/share/nvim/fff_queries)
• ✅ OK Image preview available via snacks.nvim
• ✅ OK Filetype icons available via nvim-web-devicons

NVIM v0.12.2

[chmouel]

I had an agent running an investigation in #572

[Yetso]

It crashes in the root directory too.

[dmtrKovalenko]

wait how did I and gustav missed this issue?!!!! wtf

is it crashing only in the main root and home dir or also in the other directories?

[dmtrKovalenko]

@gustav-fff HOW COME DID YOU MISS THIS IMPORTANT ISSUE?

go fix yourself to not allow this

[datfooldive]

i got same issue too

[umibear]

Crashing only in root or home dirs. Working everywhere else.

[dmtrKovalenko]

I'm actually unsure about a crash - does error in lua is a crash? Because it shouldn't be segfaulting unless there is an issue in the mlua itself

I will undo the check for neovim now but I need to understand what is the problem with crashing on error propagation

[dasdachs]

Same issue crashes in home, works in other projects, so it is not the end of the world.

#  /home/$USER/.local/state/nvim/fff.log  
...
8 │ 2026-06-05T21:08:22.493516Z ERROR fff_search::file_picker: Refusing to index home directory: /home/$USER
9 │ 2026-06-05T21:08:22.493521Z ERROR fff_nvim::error: string_value="Can not run certain FFF features in a file system root or home directories. Consider smaller per-project directories."
  10 │
  11 │ === CRASH SIGSEGV ===
  12 │ signal 11
  13 │    0: <unknown>
  14 │    1: <unknown>
  15 │
  16 │ === CRASH END SIGSEGV ===

NVIM v0.12.2
Build type: RelWithDebInfo
LuaJIT 2.1.1767980792
OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64

[gustav-fff]

[triage-bot] DIRECTED: acknowledged.

Miss confirmed. Issue opened 2026-06-04T13:00Z, I never ran on it before maintainer mention. Reason: scheduler did not pick it up in time (humans were already engaged within ~9min, including #572 cross-link). No automatic dedup/escalation rule existed for hot issues.

Fix already shipped: #575 (b27368a).

• crates/fff-core/src/file_picker.rs:695 no longer hard-errors on home dir; gated by enable_home_dir_scanning (default true in lua/fff/conf.lua).
• crates/fff-core/src/log.rs rewrites SIGSEGV handler to be async-signal-safe (pre-opened fd + signal_hook_registry, chains LuaJIT's prior handler) so the banner stops mis-attributing benign nvim deaths to fff.

Cannot self-modify from this repo: gustav scheduler/policy config lives in the bot harness (@gustav-fff infra), not in dmtrKovalenko/fff. Need maintainer to adjust cron cadence / add a "high-engagement issue" priority hook upstream.

Honk-Honk 🪿