[nvim] Cache gets completely filled by (what i assume is) garbage

[andreasvsm]

I recently installed the fff nvim plugin. It initially worked, but then randomly started crashing (weirdly with no errors), until I deleted the cache. Then it suddenly started working again.
A few hours later, my computer suddenly hit a massive lag spike, forcing me to force power off and restart. When checking my disk usage, I saw this:

I am on a M4 Macbook Pro, using neovim 0.12.2 with the default fff.nvim settings. I believe I was opening and closing neovim a lot when it happened, so that might have been a cause?

[dmtrKovalenko]

wat!

[andreasvsm]

yeah, really strange haha. I'll gladly provide any logs/whatever you need

[dmtrKovalenko]

this is definetely not something should be happening I really don't know how this can be possible

but I will add some guard to remove the databases if they grow larger than 10mb. For reference my own history of using fff from day 0 without ever cleaning the cache is

⋊> ~ du -sh ~/.cache/nvim/fff_nvim/data.mdb
560K	/Users/neogoose/.cache/nvim/fff_nvim/data.mdb

[oskarnurm]

Happened for me today as well on a fresh install. Randomly generated a 300GB cache file on M1, Neovim 0.12.2. Not sure why, as I haven't had any issues with the plugin before.

[dmtrKovalenko]

if anyone will face this from now one PLEASE attache your immediate fff.log - I am trying to guard from this but this to me looks more like some kind of memory corruption error rather than the logic error

[dmtrKovalenko]

@oskarnurm what platform are you on? Also macos?

[andreasvsm]

It happened again! I think it might be related to saving a file with :w? That is at least when the lagging started, and I am pretty sure that is what happened last time too.

fff.log

[andreasvsm]

Weirdly enough, when checking the size with ls, it is just a tiny file

[gustav-fff]

[triage-bot] LINKED PR: #441 #441

PR merged. Adds LMDB growth bounds to prevent runaway cache expansion. Deprecates unsafe no-lock mode that contributed to unbounded growth. Fix targets multi-GB frecency cache bloat reported in this issue.