panic: leveldb: resource already relesed

I have got this strange panic today. I have searched here, on GitHub, and in Google, but I have been unable to find any relevant information on this specific error.

Once the panic happened, the database became somehow corrupted and started throwing corruption on data-block errors leading to an endless restart loop. I have checked the disk (SSD) for possible hardware issues, but everything seems to be perfectly fine with it.

panic: leveldb: resource already relesed

goroutine 275853 [running]:*BasicReleaser).SetReleaser(0xc008f76800, 0x21de640, 0xc00b33d488) +0xc7*DB).newRawIterator(0xc0000fe000, 0x0, 0x0, 0x0, 0x0, 0xc00b1611d0, 0x0, 0x1, 0xc008f2bd10) +0x345*DB).newIterator(0xc0000fe000, 0x0, 0x0, 0x0, 0x0, 0x4c4306, 0xc002d09640, 0x0, 0x12e2178) +0xa5*Snapshot).NewIterator(0xc00b1611a0, 0xc002d09640, 0x0, 0x0, 0x0) +0x18e, 0xc008905ae0, 0xc008f2bc80, 0x25, 0x25, 0x25, 0x25, 0x0, 0x0) +0x114*BlockFinder).Iterate(0xc0000063a8, 0xc002d40600, 0x18, 0x20, 0xc008eab320, 0x20, 0x20, 0xc002d09c28, 0x0) +0x527*sendReceiveFolder).copierRoutine(0xc00c4d5500, 0xc005825620, 0xc0058255c0, 0xc005825680) +0x92d*sendReceiveFolder).pullerIteration.func2(0xc00c4d5500, 0xc005825620, 0xc0058255c0, 0xc005825680, 0x21f05f0, 0xc00c25e3f0) +0x50
created by*sendReceiveFolder).pullerIteration +0x4c5

panic-20210815-065956.log (1.6 MB)

PS I know that it should be spelled “released”, but I’ve just copied and pasted the error message as it is.

Sounds like a bug in the database package and/or cosmic rays (this panic has never been reported by anyone else as far as I can see). (The misspelling is in the db package so it’s easy to search for in Sentry…)

Does the bug belong in the Syncthing issue tracker, or should I report it somewhere else?

I’ve also never seen this particular panic, and I did use Syncthing on the specific device in a similar configuration previously (although this is a fresh Windows installation right now).

Honestly I don’t think it belongs anywhere unless you can reproduce it. One-off mysterious panics that might be hardware related and only happened once aren’t something we can really troubleshoot.

This happened when trying to synchronise quite a large folder. I will try enabling debug logging and then download the same folder again. Let’s see if everything goes smoothly this time.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.