-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic in 'parseKV' #383
Comments
relevant hunk of the stack trace:
|
@whyrusleeping Which version of badger are you using ? Are you using master? |
@janardhan1993 i'll have to check the exact commit we vendored from, but you can find the code we're using here: https://ipfs.io/ipfs/QmXtSA4dxoDKMzhHkwqeoBoBYASov1ZWnLQo38juKNbe3z/badger Our keys are generally around 40 bytes long if i remember correctly. cc @magik6k who has been working closely with badger for us. |
@whyrusleeping Can you also share the badger directory if possible, it would help us in debugging faster. |
@janardhan1993 I don't know if we can. Its from a user who reported the issue. I'll ask. |
@whyrusleeping It would be great if you can share a way to reproduce this. |
@janardhan1993 I'm working on it, the user was just running ipfs using badger on windows. We're using commit a9ee745 of badger. We're suspecting that its either a race condition or a memory corruption issue somewhere (theres a good amount of 'unsafe' usage in badger that we havent looked through in the skiplist) |
Looks like this wasn't an issue with Badger. Closing. |
An ipfs user reported a panic while using badger, occurring here: https://github.com/dgraph-io/badger/blob/master/table/iterator.go#L118
Initial error report (and full stack trace) here: ipfs/kubo#4512 (comment)
The text was updated successfully, but these errors were encountered: