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

GAPIS crashes in deviceinfo on Windows with AMD cards. #1867

Closed
AWoloszyn opened this issue May 7, 2018 · 7 comments
Closed

GAPIS crashes in deviceinfo on Windows with AMD cards. #1867

AWoloszyn opened this issue May 7, 2018 · 7 comments
Labels
bug has-workaround This issue has not been fixed to our liking, but has been worked around for now.

Comments

@AWoloszyn
Copy link
Contributor

I am not sure exactly what set of AMD cards are failing, but I have run into this on windows.

The issue looks to be here:
https://github.com/google/gapid/blob/master/core/os/device/deviceinfo/cc/windows/query.cpp#L77

Commenting out the lines fixes it, but obviously is not the right choice. I have tried a number of fixes, and have not managed to figure out what the root cause is.

@AWoloszyn
Copy link
Contributor Author

Added a blacklist for the known bad cases.

If anyone runs into any more, please let me know so I can expand the blacklist.

@AWoloszyn
Copy link
Contributor Author

Removing P1, since this is worked around in master.

@AWoloszyn AWoloszyn removed the P1 label May 8, 2018
@farnoy
Copy link

farnoy commented May 13, 2018

@AWoloszyn I'm not sure I have this exact issue, but are you certain this blacklist works? query::osName() is backed by Window's GetVersionEx, which is deprecated and not supposed to report anything above major version 8, unless you set special assembly.

@AWoloszyn
Copy link
Contributor Author

I have tested this on 2 separate Windows 10 machines, and both have returned Windows 10 as their OS string. That being said I am not 100% confident that this will work in every case.

The symptom of this bug is that the UI will just fail to open. You can run gapid --console, and see the server trying to start up, and then crashing immediately.

This fix only exists in the latest master, and not in any shipped binary, but we are trying to get a build together soon.

@farnoy
Copy link

farnoy commented May 14, 2018

Fair enough, my issue is a different one.

@farnoy
Copy link

farnoy commented May 18, 2018

Just FYI, whatever my issue was, it was fixed in 1.1.0.

@AWoloszyn
Copy link
Contributor Author

There are a ton of changes in 1.1 so it may be hard to pinpoint exactly what fixed your issue, but regardless that is great to hear.
Thanks for taking the time to let us know!

@AWoloszyn AWoloszyn added the has-workaround This issue has not been fixed to our liking, but has been worked around for now. label May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug has-workaround This issue has not been fixed to our liking, but has been worked around for now.
Projects
None yet
Development

No branches or pull requests

2 participants