-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat(events): GPU interface #10162
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
feat(events): GPU interface #10162
Conversation
* create tag for GPU name and vendor
8db450b
to
6eb6f0b
Compare
relies on getsentry/sentry#10162
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm but nvidia logo seems streched
@mitsuhiko you are right. Although fixed still looks a bit odd: |
knownData.unshift(['?Vendor Id', vendor_id]); | ||
} | ||
|
||
if (id > 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This condition could be combined with the one above it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You just caught a bug there! I should be checking for: vendor_id
.
This is due to Unity serialization not handling int?
, so type is not nullable and 0
will be sent :
It will be the case until we get away from Unity.JsonUtility
Examples:
Although the Unity API is called
SystemInfo.graphicsDeviceVendor
it seems to return the driver vendor instead.The
SystemInfo.graphicsDeviceName
API returns in a single string what we would expect to be vendor, name and version.The plan is to let the data come in and once we have a enough sample, write the normalization code to better display this.
Note that GPU context was added with the smallest priority:
https://github.com/getsentry/sentry/pull/10162/files#diff-af6a04783ec9ae8b4cff8f0437a50e46R240
This is relevant because in case an event came in with user, runtime, os and device, GPU wouldn't be visible.