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

Closing windows can cause segfaults or other bad exit codes #12

Open
cyanpelican opened this issue Feb 19, 2019 · 2 comments
Open

Closing windows can cause segfaults or other bad exit codes #12

cyanpelican opened this issue Feb 19, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@cyanpelican
Copy link
Collaborator

For example on Mac, closing a window causes the following:
libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument
Abort trap: 6

@natevm
Copy link
Owner

natevm commented Apr 10, 2019

I can reproduce this error on my machine. Will take a look...

@natevm natevm added the bug Something isn't working label Apr 10, 2019
@natevm
Copy link
Owner

natevm commented Apr 10, 2019

I believe this is fixed.

In destroy_window in the GLFW wrapper class, the GLFW window was being destroyed after destroying its swapchain. Switching this order (destroying the window before destroying its swapchain) seems to have fixed the issue.

@cyanpelican If you get a chance, could you see if you get the same assertion as reported above on the latest version of development?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants