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

Segmentation Fault on OSX on main branch #8211

Closed
ManevilleF opened this issue Mar 25, 2023 · 7 comments · Fixed by #8223
Closed

Segmentation Fault on OSX on main branch #8211

ManevilleF opened this issue Mar 25, 2023 · 7 comments · Fixed by #8223
Labels
C-Bug An unexpected or incorrect behavior O-MacOS Specific to the MacOS (Apple) desktop operating system

Comments

@ManevilleF
Copy link
Contributor

ManevilleF commented Mar 25, 2023

Possibly related to #8144
Closed by #8180 and #8223

Bevy version

Crash on: 0.11-dev (the main branch) commit 289fd1d
Doesn't crash on: 0.10 commit 4f16d6e

EDIT: After investigation it seems it crashes since commit 6a85eb3 (#6529)

System information

  • rust 1.68.0
  • system info:
    • os: "MacOS 13.0.1 "
    • kernel: "22.1.0"
    • cpu: "Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz"
    • core_count: "6"
    • memory: "16.0 GiB"
  • adapter info:
    • name: "AMD Radeon Pro 5300M"
    • vendor: 0
    • device: 0
    • device_type: DiscreteGpu
    • backend: Metal

What you did

I run any bevy example

What went wrong

  • what were you expecting?

The example should run

  • what actually happened?

The examples compile but crash at runtime with a segmentation fault:

[1] 33800 segmentation fault cargo run --example $EXAMPLE_NAME

The (empty) window appears for a split second before the crash.

Additional information

This crash only happens on the mainbranch, the 0.10 release and prior versions did not

@ManevilleF ManevilleF added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Mar 25, 2023
@mockersf
Copy link
Member

can't reproduce on a Mac with an m1

@ManevilleF
Copy link
Contributor Author

@mockersf After investigation it seems it crashes since commit 6a85eb3 (#6529) So the addition of bevy_gizmos

@mockersf
Copy link
Member

mockersf commented Mar 25, 2023

Could you check which commit you are running on? the commit you mention in the issue is before gizmos were added. There was also a fix a few commits after, so could you retry with latest main?

@ManevilleF
Copy link
Contributor Author

Could you check which commit you are running on? the commit you mention in the issue is before gizmos were added. There was also a fix a few commits after, so could you retry with latest man?

#8151 does'nt fix the crash but I just checked out @devil-ira fix #8180 and it works !

@mockersf
Copy link
Member

just tried gizmo related examples, 2d_gizmos segfault for me but not 3d_gizmos

@ManevilleF
Copy link
Contributor Author

just tried gizmo related examples, 2d_gizmos segfault for me but not 3d_gizmos

With the fix ?

Because for me, on main, any example segfaults, even the examples unrelated to gizmos like UI or sprite examples

@alice-i-cecile alice-i-cecile added O-MacOS Specific to the MacOS (Apple) desktop operating system and removed S-Needs-Triage This issue needs to be labelled labels Mar 25, 2023
@rparrett
Copy link
Contributor

Any example with a 2d camera is segfaulting for me.

I think this is a duplicate of #8144.

#8151 fixed a separate bug that came up while investigating that one.

#8180 only mitigates it for examples that do not spawn gizmos. 2d_gizmos still segfaults.

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-MacOS Specific to the MacOS (Apple) desktop operating system
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants