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

error: process didn't exit successfully: target\debug\examples\breakout.exe (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION) #5998

Open
diyajoy opened this issue Sep 16, 2022 · 5 comments
Labels
C-Bug An unexpected or incorrect behavior O-Windows Specific to the Windows desktop operating system P-Crash A sudden unexpected crash

Comments

@diyajoy
Copy link

diyajoy commented Sep 16, 2022

Bevy version

0.8.1

Relevant system information

If you cannot get Bevy to build or run on your machine, please include:

Rust version: rustc 1.65.0-nightly (happens with stable as well)

What you did

I was following the setup instructions here.
However, I wasn't able to cargo run --features bevy/dynamic successfully. Following this issue, I added the following lines to my config.toml to disable share generics, but didn't see any change after re-running the sample:

[target.x86_64-pc-windows-msvc]
linker = "rust-lld.exe"
rustflags = ["-Zshare-generics=off"]

What went wrong

When I ran cargo run --features bevy/dynamic, I got a segmentation fault:
error: process didn't exit successfully: target\debug\examples\breakout.exe (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
Segmentation fault

Additional information

I don't see this issue when running an empty Hello World project with Bevy as a dependency. I'm also quite new to Rust so I could be missing something simple!

Edit: If I run the sample with nothing in my config.toml, I get the following error instead:
note: LINK : fatal error LNK1189: library limit of 65535 objects exceeded

@diyajoy diyajoy added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Sep 16, 2022
@Sheepyhead
Copy link
Contributor

Which operating system are you running this on?

@diyajoy
Copy link
Author

diyajoy commented Sep 16, 2022

Windows 10 Pro, 64 bit

@bjorn3
Copy link
Contributor

bjorn3 commented Sep 16, 2022

There is a compatibility issue between ldd and the xinput dll that bevy depends on with llvm and microsoft blaming each other for this issue I believe. You can either disable the bevy_gilrs feature or switch away from lld.

@bjorn3 bjorn3 added O-Windows Specific to the Windows desktop operating system P-Crash A sudden unexpected crash labels Sep 16, 2022
@diyajoy
Copy link
Author

diyajoy commented Sep 16, 2022

Thank you! How do I disable the bevy_gilrs feature?

@djeedai
Copy link
Contributor

djeedai commented Sep 17, 2022

LNK1189 is a known (and annoying) limitation of the Microsoft linker. There's no way around it unfortunately.

@alice-i-cecile alice-i-cecile removed the S-Needs-Triage This issue needs to be labelled label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Bug An unexpected or incorrect behavior O-Windows Specific to the Windows desktop operating system P-Crash A sudden unexpected crash
Projects
None yet
Development

No branches or pull requests

5 participants