Closed Bug 798048 Opened 8 years ago Closed 3 years ago

Put AdapterVendorID and AdapterDeviceID in the crash reports (implement GfxInfo)

Categories

(Firefox OS Graveyard :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: hub, Unassigned)

References

Details

We need AdapterVendorID and AdapterDeviceID in the crash report.

See https://bugzilla.mozilla.org/show_bug.cgi?id=777187#c25
Adding to the summary that this (probably) needs GfxInfo.

mwu, bug 777187 comment #29 says you have taken a look at this at some point, who can we contact to work on this? How difficult is it?
Summary: Put AdapterVendorID and AdapterDeviceID in the crash reports. → Put AdapterVendorID and AdapterDeviceID in the crash reports (implement GfxInfo)
Joe can you tell us what would be most useful here? Does someone from gfx want to take this bug?
Flags: needinfo?(joe)
FYI, from the crash analysis POV, we 1) have those fields already shown in public crash report data on the website and 2) will work to get some kind of correlation data or "signature summary" data using those fields to show on which graphics chips what percentage of those crashes occur.
As soon as there will be devices with different chips where we ship B2G, this will be very helpful - before that, I guess devices to which people deploy custom builds will be even easier to pick out through this.
The easiest way to implement this is using GfxInfo, and I suggest that it just be copied directly from the Android version, doing exactly the same things (so long as they work).
Flags: needinfo?(joe)
(In reply to Joe Drew (:JOEDREW! \o/) from comment #4)
> The easiest way to implement this is using GfxInfo, and I suggest that it
> just be copied directly from the Android version, doing exactly the same
> things (so long as they work).

Android's GfxInfo is implemented through AndroidBridge which talks to Java, which Gonk doesn't have.

We can probably just query the graphics drivers directly, however.
Is this optional for V1, or required? If required for useful crash submissions, please nominate for blocking-basecamp.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.