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

[BUG] Instant error STATUS_ACCESS_VIOLATION on Windows with Rust lib #116

Closed
ghost opened this issue Mar 14, 2024 · 8 comments
Closed

[BUG] Instant error STATUS_ACCESS_VIOLATION on Windows with Rust lib #116

ghost opened this issue Mar 14, 2024 · 8 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers rust

Comments

@ghost
Copy link

ghost commented Mar 14, 2024

I got instant STATUS_ACCESS_VIOLATION while running the memchr_stringzilla benchmark, it works totally fine with WSL2 on Windows but not on Windows itself.

@ashvardanian
Copy link
Owner

Thanks for submitting the issue, @0xqd! Can you please clarify if you've detected an issue with the benchmark or the library itself?

@ghost
Copy link
Author

ghost commented Mar 14, 2024

@ashvardanian The repo I use to reproduce is the one from you:
https://github.com/ashvardanian/memchr_vs_stringzilla

Environment the script run on:

cargo --version
cargo 1.76.0 (c84b36747 2024-01-18)

winver
Version 22H2 (OS Build 22621.1702)

Error

Gnuplot not found, using plotters backend
Benchmarking search-forward/stringzilla::find
Benchmarking search-forward/stringzilla::find: Warming up for 10.000 s
Error: Failed to receive message from Criterion.rs benchmark bench

Caused by:
    An existing connection was forcibly closed by the remote host. (os error 10054)

I edit the title of the post to proper error message

Minimal reproducible code:

#[cfg(test)]
mod tests {
    use stringzilla::{sz};

    #[test]
    fn test_stringzilla() {
        sz::find("hello", "l");
    }
}

Error:

process didn't exit successfully: `<path>\b2d8f6d198f2a16b.exe app::tests::test_stringzilla --format=json --exact -Z unstable-options --show-output` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

@ghost ghost changed the title [BUG] Instant STATUS_ACCESS_VIOLATION on Windows with Rust lib [BUG] Instant error (os error 10054) on Windows with Rust lib Mar 14, 2024
@ghost ghost changed the title [BUG] Instant error (os error 10054) on Windows with Rust lib [BUG] Instant error STATUS_ACCESS_VIOLATION on Windows with Rust lib Mar 14, 2024
@ashvardanian ashvardanian added bug Something isn't working good first issue Good for newcomers rust labels Mar 14, 2024
@ashvardanian
Copy link
Owner

@0xqd What kind of Windows machine are you running on? Is that a Aarch64 Arm-based machine by any chance?

@ashvardanian
Copy link
Owner

This might be coming from Rust itself, there is a similar issue reported for Arm-based Windows setups: rust-lang/rust#118462

@ghost
Copy link
Author

ghost commented Mar 14, 2024

@ashvardanian it's x86_64 with Intel 13900K. Yeah I have seen that report, not sure if you have the solution.

@ashvardanian
Copy link
Owner

Is that issue still bothering you, @0xqd? I can try running it on a Windows machine later today 🤗

@ashvardanian ashvardanian self-assigned this Apr 17, 2024
@ghost
Copy link
Author

ghost commented Apr 17, 2024

hi there @ashvardanian, instead of using Windows just for convenience, I switch everything to Linux to be problem free now.

@ashvardanian
Copy link
Owner

That should make your life easier down the road 🤗

ashvardanian added a commit to ashvardanian/stringzilla-benchmarks-rs that referenced this issue Apr 18, 2024
@ghost ghost closed this as completed May 1, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers rust
Projects
None yet
Development

No branches or pull requests

1 participant