-
Notifications
You must be signed in to change notification settings - Fork 4
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
Eventual crash when reading a lot of chunk data quickly #7
Comments
I should also mention that this doesn't happen in dev/debug builds(presumably because it's too slow). It does happen in release builds with the following settings: # Commenting 'strip' and uncommenting 'debug' still causes a crash
[profile.release]
strip = true
opt-level = 3
codegen-units = 1
lto = true
# debug = "full" |
I can't seem to reproduce this on my computer using your files, and I'm not really sure as to what the issue could be. Either way, I have another big refactor of simdnbt::borrow I mostly wrote a while ago that significantly improves performance again (it still has lots of unsafe but it reduces the allocations at least), so I'm assuming that'll probably fix this issue once I finish it up. |
That's a bummer. Though, I'm glad to hear about the future improvements in hopes they'll get rid of the issue. |
According to git bisect |
If you'd like to have another go at trying to reproduce this, here's my crate. |
Alright so as I was working on my other branch I realized it'd be a good idea to add a fuzzer and it turned out to be way more effective than I anticipated. I ran cargo-fuzz on the master branch too, and it does actually find an input that triggers a buffer overflow (which I believe is the same as this issue).
(I ran it through cargo-fuzz's minifier though I'm sure it could be minified more). Tbh though, figuring out the root cause of this is probably more effort than it's worth since I'm going to merge my other branch that doesn't have the same issue soon. |
That's pretty cool! |
This issue appears first in version 0.5.0.
Here's the stack and analysis from WinDbg.
Here's a somewhat incomplete minimal reproduction: main.rs and regions.
Note: You might need more region files to reproduce this, depending on how powerful your machine is.
The text was updated successfully, but these errors were encountered: