-
Notifications
You must be signed in to change notification settings - Fork 649
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
sweep increased allocation count with v1.3.4 #214
Comments
I have started to see the same issue after upgrading to v1.3.4. And it's appearing on my Github workflow builds very frequently. But I was able to reproduce on my dev machine only once.
|
Since the crash seems to happen inside the golang runtime, I think it would be wise to open an issue on golang/go as well to put it on their radar |
cc @jpbetz |
We can confirm this happening in containerd after recent upgrade to 1.3.4 as well |
Can others test https://github.com/jrick/bbolt/tree/memfix? It has fixed these issues for some of our usage, but I'm unsure if it's a complete fix. I'm also not entirely sure what the problem was to begin with and how or why this branch behaves differently. |
@gyuho, should #201 be reverted while this issue remains? if I'm reading this correctly, master and the latest release are still known bad against go 1.14.x (which #201 was fixing) and go1.13 ("At first we were running the tests with Go 1.14, then tried to go back to version 1.13, but the would still pop up.") |
Yes, what's stable for us is: Go 1.13.x and |
@Roasbeef Sorry to ping you here. I was curious how the experiment went. Our upgrade to go1.14 is blocked on this and we'd like to help if we can. |
@gouthamve you can try out my branch as well if you're interested in testing. I'm still looking for feedback on it before I open another pull request. This command will apply the replacement for the test:
|
@jrick's |
Signed-off-by: Gyuho Lee <[email protected]>
@Roasbeef could you share the tests? Is that something that can be added to bbolt as regression testing? |
@gyuho I think this is the test that was used to repro: https://github.com/matheusd/bbolt-sweep-bug/blob/master/my_test.go |
@gyuho I've committed a modified version of that test to my PR. |
Is it okay if we use go 1.14.x and bbolt 1.3.3? Has anyone experimented with that? Please let me know. |
This is currently cropping up in one of my projects. I see that two days ago #220 was merged to correct this. I am not familiar with this project's timeline for patch releases: when can we expected this to be tagged for a version? |
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
We had once updated bbolt from v1.3.3 to v1.3.4 in containerd#4134, but reverted to v1.3.3 in containerd#4156 due to "fatal error: sweep increased allocation count" (etcd-io/bbolt#214). The issue was fixed in bbolt v1.3.5 (etcd-io/bbolt#220). Signed-off-by: Akihiro Suda <[email protected]>
We had once updated bbolt from v1.3.3 to v1.3.4 in containerd#4134, but reverted to v1.3.3 in containerd#4156 due to "fatal error: sweep increased allocation count" (etcd-io/bbolt#214). The issue was fixed in bbolt v1.3.5 (etcd-io/bbolt#220). Signed-off-by: Akihiro Suda <[email protected]>
We had once updated bbolt from v1.3.3 to v1.3.4 in containerd#4134, but reverted to v1.3.3 in containerd#4156 due to "fatal error: sweep increased allocation count" (etcd-io/bbolt#214). The issue was fixed in bbolt v1.3.5 (etcd-io/bbolt#220). Signed-off-by: Akihiro Suda <[email protected]>
We had once updated bbolt from v1.3.3 to v1.3.4 in containerd#4134, but reverted to v1.3.3 in containerd#4156 due to "fatal error: sweep increased allocation count" (etcd-io/bbolt#214). The issue was fixed in bbolt v1.3.5 (etcd-io/bbolt#220). Signed-off-by: Akihiro Suda <[email protected]> (cherry picked from commit bebfbab) Signed-off-by: Akihiro Suda <[email protected]>
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
- need fix from etcd-io/bbolt#214 and etcd-io/bbolt#220 for full go 1.14 compat
After updating our project to the latest version of
bbolt
which includes #201, we've started running into this runtime error in our tests:So far, it only seems to happen about every 1 in 5 test runs. At first we were running the tests with Go 1.14, then tried to go back to version 1.13, but the issue would still pop up. Only after downgrading to
bbolt v1.3.3
does the issue seem to disappear. Given that the issue seems to persist using the last two major versions of Go, it may be the case that #201 uncovered another underlying issue, or the changes in the PR are actually triggering this new error.We're working on creating a reproducible program to trigger this warning.
The full trace of this error in our tests can be found here: https://paste.ubuntu.com/p/XNgrZ49dbw/
The text was updated successfully, but these errors were encountered: