-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Segmentation fault when running 2d_gizmos example #8144
Comments
Same here. It crashed with
|
Should be introduced by pr #6529 |
@cwfitzgerald This seems to be coming from inside |
You can try running with |
The
Interestingly,
|
Sorry I gave the wrong env, it's |
Oops. I didn't specialize the 2d pipeline on HDR. I'll have a PR up shortly to fix that. edit: #8151 |
Cool, seems like this was unrelated to the M1 segfaulting which is still happening in every example with a 2d camera as far as I can tell. (didn't test them all) |
Yeah, I figured. I don't see a reason why this happens as the 2d gizmo pipeline really doesn't do anything special and is mostly the same as the 3d one, except for not using a depth stencil and alpha blending being enabled. Have you tried running it with |
Yeah, that emits a
message, but no validation errors. |
I'm getting this same issue when running |
I think issue this can now be closed. EDIT: Nvm, I see there's another issue beside the HDR specialization. |
I think this issue comes from upstream somewhere but it's a crash affecting enough users that it's worth trying to fix here. |
I have 2 ideas that might hopefully solve this.
|
Tried both, still segment fault for me. |
Shucks. I can't think of anything else :( |
I was able to fix the issue for me with #8223 |
# Objective Avoid queuing empty meshes for rendering. Should prevent #8144 from triggering when no gizmos are in use. Not a real fix, unfortunately. ## Solution Add an `in_use` field to `GizmoStorage` and only set it to true when there are gizmos to draw.
Bevy version
lastest main(caa6622).
[Optional] Relevant system information
AdapterInfo { name: "Apple M1", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
SystemInfo { os: "MacOS 13.0 ", kernel: "22.1.0", cpu: "Apple M1", core_count: "8", memory: "16.0 GiB" }
What you did
cargo run --example 2d_gizmos
What went wrong
segmentation fault
P.S.
3d_gizmos
example works fine.The text was updated successfully, but these errors were encountered: