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

MacOS Clang: Updating from 0.9.9.9 to latest causes memory corruption. #1234

Open
SamCZ opened this issue Jan 26, 2024 · 3 comments
Open

MacOS Clang: Updating from 0.9.9.9 to latest causes memory corruption. #1234

SamCZ opened this issue Jan 26, 2024 · 3 comments

Comments

@SamCZ
Copy link

SamCZ commented Jan 26, 2024

Hi, today I updated from 47585fd to latest and weird things started happening.

Rn I use glm for only projection, view, and simple vector math, nothing really special.

After the update my second engine viewport stopped working and while dragging imgui windows I get swapchain errors and also imgui draw errors.
image
image

Im not sure how this can happen, but after reverting back to the old commit, it started working like a charm.
I also tried disabling fast math, but it did nothing.

Im using C++20 Clang on Macbook pro M2 with Clion.

I will try to post more info when I investigate more, but I just wanted to show you guys this so we can quicky resolve it.

Edit: To get glm working on nevest I needed to set the cmake option for GLM_ENABLE_CXX_20 otherwise it would not compile because errors with c++98 compat.

@Tachi107
Copy link

Would you be able to use git bisect to find the first bad commit?

@SamCZ
Copy link
Author

SamCZ commented Jan 28, 2024

Would you be able to use git bisect to find the first bad commit?

Just yesterday in the night I found what was causing the crashes, its not because of glm, but even with that not crashing, my screen is blank. I will today do the bisect and let you know.

@christophe-lunarg christophe-lunarg linked a pull request Feb 6, 2024 that will close this issue
@christophe-lunarg christophe-lunarg removed a link to a pull request Feb 6, 2024
@SamCZ
Copy link
Author

SamCZ commented Feb 6, 2024

Sorry for still not replying, I could not yet do it. But I promise in few days I will do it. Meanwhile we have still the old commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants