-
Notifications
You must be signed in to change notification settings - Fork 276
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
Segmentation fault on inserts #156
Comments
Hi @dave11ar, thanks for reporting! I tried running your repro on my own machine (details below), but failed to trigger any crashes. I tried 100 runs with your exact parameterization, and 100 runs with 20 threads, which is the number of CPUs on my machine. If you're able to provide any more reproduction or debugging tips, I'd be happy to try digging further.
|
I have reproduced the described bug. Here's the backtrace
And my CPU specs:
If you need more information from me, please reach out. |
Thanks @Explosiontime202. It seems we have very similar machines, but I'm still having trouble reproducing the crash. A few questions.
Where my compiler version is
|
Hi, We are facing the same issue on x86_64 and e2k architectures. This cmd line is usually enough to reproduce the issue:
Test finishes with |
Hi @ivafanas, @Explosiontime202, @dave11ar. I put up a fix for the segfault in 91b9c2d. I was able to reproduce the issue on an ec2 machine (using @ivafanas's repro) and verified that it no longer shows up over hundreds of runs. If you have a chance to run on your own and verify that would be great. Thanks for reporting! |
Hi, We are testing libcuckoo regularly on our hardware for a month after the fix and there is no crash anymore. Thank you! |
That's so great to hear @ivafanas, thank you! Will mark as closed. |
When I run my benchmarks on processors with big amount of cores:
I got segmentation fault on 196 line in bucket_container.hh (bucket_container
operator[]
)I was able to reproduce this with slightly modified (change initial capacity of tables from g_numkeys to 0) stress tests from your repo by running
stress_checked.cc
with keys--power 16 --thread-num 48 --time 15 --disable-deletes --disable-updates --disable-finds
This issue is for v0.3.1 tag
The text was updated successfully, but these errors were encountered: