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

Windows crash: 0xc0000005 (STATUS_ACCESS_VIOLATION) #68

Open
terrybrash opened this issue Aug 26, 2023 · 1 comment
Open

Windows crash: 0xc0000005 (STATUS_ACCESS_VIOLATION) #68

terrybrash opened this issue Aug 26, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@terrybrash
Copy link

terrybrash commented Aug 26, 2023

Describe the bug
The haptic example causes the application to crash with 0xc0000005 (STATUS_ACCESS_VIOLATION) after event_loop is completed.

To Reproduce
Steps to reproduce the behavior:

  1. Setup the haptic example
  2. Change main to the following:
fn main() {
    pasts::block_on(event_loop());

    loop {
        println!("hello world");
        std::thread::sleep(std::time::Duration::from_millis(500));
    }
}
  1. cargo run and then trigger the MenuR event on a connected controller.
  2. Should crash almost immediately.

Expected behavior
No crash. It should print "hello world" forever after triggering MenuR.

Desktop:

  • OS: Windows 10 (10.0.19045 Build 19045)
  • Stick version: v0.12.4
@AldaronLau
Copy link
Member

@terrybrash Thank you for reporting, I will look into it when I have a chance.

@AldaronLau AldaronLau added the bug Something isn't working label Aug 28, 2023
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