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

vkcube: seg faults with the dev sim layer enabled #1183

Open
johnzupin opened this issue Sep 22, 2020 · 2 comments
Open

vkcube: seg faults with the dev sim layer enabled #1183

johnzupin opened this issue Sep 22, 2020 · 2 comments

Comments

@johnzupin
Copy link
Contributor

This might not be related to vkconfig but I though I would create an issue here first to see if anyone can replicate.

Creating a new layer config with dev sim layer enabled and trying to run vkcube cause vkcube to seg fault.

I'm using this json file from Sasha W's blog post here

This issue only seems to happen on windows, vkcube runs fine with dev sim and these settings on linux.

@johnzupin johnzupin added OS - Windows Windows specific bug Project - vkconfig Issues related to vkconfig labels Sep 22, 2020
@christophe-lunarg christophe-lunarg added bug and removed Project - vkconfig Issues related to vkconfig OS - Windows Windows specific bug labels Sep 23, 2020
@christophe-lunarg christophe-lunarg changed the title vkconfig: vkcube seg faults with the dev sim layer enabled vkcube: seg faults with the dev sim layer enabled Sep 23, 2020
@christophe-lunarg
Copy link
Contributor

The configuration used was an Mali T880 one. Such configuration are very different from desktop which I think explain the crash. I tried with a Radeon RX 570 configuration and I could not reproduce the crash.

This said, vkcube should not require any specific features or a large number of resources for anything so it should probably be improved.

It would be great if the Vulkan SDK could ship with a "minimum bar" configuration that we could use to check that vkcube is working and to experience a relevant workflow for devsim so that we could make using this layer nice for the Vulkan developers.

@jeremyk-lunarg
Copy link
Contributor

Ran this without using vkconfig and still got a crash.
Tried running with validation layers, but the validation layers didn't throw any warnings.

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

No branches or pull requests

3 participants