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

Example shader/array_texture crash with wgpu error #2122

Closed
giusdp opened this issue May 6, 2021 · 6 comments
Closed

Example shader/array_texture crash with wgpu error #2122

giusdp opened this issue May 6, 2021 · 6 comments
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior P-Crash A sudden unexpected crash
Milestone

Comments

@giusdp
Copy link
Contributor

giusdp commented May 6, 2021

Bevy version

v0.5.0 commit 7d0e98f

Operating system & version

Manjaro Linux

What you did

Ran the example array_texture with cargo run --example array_texture

What you expected to happen

The example to work.

What actually happened

After opening the window at first, it quickly crashed.

Additional information

The console log errors:

wgpu error: Validation Error

Caused by:
    In Device::create_bind_group
    texture binding 0 expects dimension = D2, but given a view with dimension = D2Array


thread 'Compute Task Pool (0)' panicked at 'Handling wgpu errors as fatal by default', /home/giusdp/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.8.0/src/backend/direct.rs:1955:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'task has failed', /home/giusdp/.cargo/registry/src/github.com-1ecc6299db9ec823/async-task-4.0.3/src/task.rs:368:45
zsh: segmentation fault (core dumped)  cargo run --example array_texture
@giusdp giusdp added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels May 6, 2021
@MinerSebas
Copy link
Contributor

Bisecting the Repo, that Panic appeared after the move to wgpu 0.8 in #1959

@bjorn3 bjorn3 added P-Crash A sudden unexpected crash A-Rendering Drawing game state to the screen and removed S-Needs-Triage This issue needs to be labelled labels May 6, 2021
@cart cart added this to the Bevy 0.6 milestone May 6, 2021
@mockersf
Copy link
Member

mockersf commented May 8, 2021

@jakobhellermann I think it's an issue in reflection, would #2130 also fix this case?

@jakobhellermann
Copy link
Contributor

jakobhellermann commented May 8, 2021

@jakobhellermann I think it's an issue in reflection, would #2130 also fix this case?

Yep, on #2130 the example works again.

@superdump
Copy link
Contributor

#2130 fixes this for me too on macOS.

@KoomZog
Copy link

KoomZog commented Oct 2, 2021

I'm having the same issue as OP. I'm on Bevy main (on win 10). This is the error message I got: https://pastebin.com/iVbceafu
Is there a fix for this at the moment, or should I just wait for 0.6?

@cart
Copy link
Member

cart commented Dec 14, 2021

Closing this because the old renderer has been removed and the new renderer relies way less on reflection, so this shouldn't be an issue anymore. Feel free to open a new issue if you still have problems.

@cart cart closed this as completed Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior P-Crash A sudden unexpected crash
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants