Skip to content
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

Crash with FATAL Level #447

Closed
knight-ryu12 opened this issue May 23, 2020 · 3 comments
Closed

Crash with FATAL Level #447

knight-ryu12 opened this issue May 23, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@knight-ryu12
Copy link

Describe the bug
I am not sure what causes this behavior.

To Reproduce
Unable to provide.

Environment information:

  • OS: ArchLinux
  • RAM: 4GB
  • Cores: 4 Cores
  • Type: X86_64
  • HORNET version 0.4.0-rc10

Additional context
https://ybin.me/p/448c41cdc3ff5937#S1k1vdQOv137FCPQWezUm9wvIft7XoEpKkj8Dg037zc=

@knight-ryu12 knight-ryu12 added the bug Something isn't working label May 23, 2020
@muXxer
Copy link
Collaborator

muXxer commented May 26, 2020

Looks like an unsafe pointer problem in bbolt.
Maybe this issue is fixed since we changed bbolt settings in #451.
Should this problem occur again, please open a new issue report.

@muXxer muXxer closed this as completed May 26, 2020
@muXxer
Copy link
Collaborator

muXxer commented May 26, 2020

There seems to be an unmerged fix for the problem.
etcd-io/bbolt#220

@knight-ryu12
Copy link
Author

yeah, looks like it. thanks for an insight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants