ShaDa file corruption on nightly about neovim

[AThePeanut4]

@bfredl Can confirm #29221 fixes it, thanks!

[bfredl]

@AThePeanut4 would you mind try #29221 and see if it helps?

[tris203]

I am seeing similar issues on Ubuntu. I had had to clear the ShaDA folder multiple times since around a week or so ago

[axelhj]

I've seen the same error message frequently since around v0.11 (nightly/build from master) but also before that. A plugin that I use write shada on VimLeave. I see #8587 when running Neovim on Windows 11 and wonder if there is a link with that shada error at least in some instances. I am not sure why those tmp-files are used in the first place.

[jgilardi]

Seeing the same issue on the same version (NVIM v0.11.0-dev-168+ge20c5fba2) on Windows

[metiftikci]

for me, removing AppData/Local/nvim-data/shada folder resolved the problem

Edit: but then i still see the same error after a while. i think neovim saving the file in wrong format

[bfredl]

some relatively recent changes to reading/writing shada was #29093 and #29016 (more likely the former causing issues at is is a more complex refactor)

[AThePeanut4]

I'm also getting this, but only on Windows, and it seems to be a read issue not a write issue - if I copy the main.shada file that was giving E576 errors over to WSL, it works without issue. Reverting to the v0.10 release also works correctly, with that same main.shada file.

I'm using the latest git commit on WSL (d7651b2) and the latest nightly on Windows (f69937f).

[AThePeanut4]

@bfredl Just did a bisect, and I can confirm the first bad commit is indeed 7e44ab6 (#29093).

[melMass]

I think this issue also affects stable 0.10.0....
I was experiencing it a lot but haven't since I'm building from source