Closed
Bug 1167693
Opened 10 years ago
Closed 10 years ago
Strange AdapterHexIDs with spaces
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
mozilla41
Tracking | Status | |
---|---|---|
firefox41 | --- | fixed |
People
(Reporter: peterbe, Assigned: kats)
Details
(Whiteboard: [gfx-noted])
Attachments
(2 files)
56.75 KB,
image/png
|
Details | |
1.16 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
See, for example, this crash: https://crash-stats.mozilla.com/report/index/02a8cec2-88fc-4b65-b6da-ccf272150522
It has, under "App Notes"::
AdapterVendorID: 0x10de, AdapterDeviceID: 0x fe9
This space means we can't ever find it a graphics adapter name for this. E.g. See "Graphics Adapter Report" tab on https://crash-stats.mozilla.com/report/list?product=Firefox&signature=mozilla%3A%3Aipc%3A%3ASerializeInputStream%28nsIInputStream*%2C+mozilla%3A%3Aipc%3A%3AInputStreamParams%26%2C+nsTArray%3Cmozilla%3A%3Aipc%3A%3AFileDescriptor%3E%26%29
Updated•10 years ago
|
Component: XPCOM → Graphics
Assignee | ||
Comment 1•10 years ago
|
||
Apparently we have an API to spoof the adapter device ID: http://mxr.mozilla.org/mozilla-central/source/widget/nsIGfxInfoDebug.idl#14
It's possible some add-on or user has set this to a bad value. I'm not sure if it's worth trying to deal with this. WONTFIX?
Assignee | ||
Updated•10 years ago
|
Whiteboard: [gfx-noted]
Comment 2•10 years ago
|
||
This crash was from peterbe's computer, so feel free to ask him if he has something weird configured!
Reporter | ||
Comment 4•10 years ago
|
||
Kartikaya,
What's your question? I have add-ons installed. Several of them. None are called Screw-Up-The-Hex-Values :)
Flags: needinfo?(peterbe) → needinfo?(bugmail.mozilla)
Assignee | ||
Comment 5•10 years ago
|
||
Shoulda guessed it wouldn't be that obvious :)
If you start Firefox with a clean profile and trigger a crash, does the crash report still have the spaces in the AdapterHexIDs? Alternatively, if you have a build you can debug, stick a breakpoint at http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/GfxInfo.mm?rev=f25e20a0f238#396 and see if it gets hit. If there's no spoofing happening, then I'd be interested in knowing if the value obtained at http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/GfxInfo.mm?rev=f25e20a0f238#96 has the space, or if the space is somehow inserted afterwards. As far as I can tell there's no way this should be happening unless there's some spoofing going on.
Flags: needinfo?(bugmail.mozilla) → needinfo?(peterbe)
Reporter | ||
Comment 6•10 years ago
|
||
Here's another crash [0] I just made with 41.0a1 (2015-06-01). It has no extensions installed at all.
[0] https://crash-stats.mozilla.com/report/index/ea292326-fda9-4804-8178-9f5132150601
Flags: needinfo?(peterbe)
Assignee | ||
Comment 7•10 years ago
|
||
Doh.
Assignee: nobody → bugmail.mozilla
Attachment #8613610 -
Flags: review?(mstange)
Comment 8•10 years ago
|
||
Comment on attachment 8613610 [details] [diff] [review]
Patch
Review of attachment 8613610 [details] [diff] [review]:
-----------------------------------------------------------------
nice
Attachment #8613610 -
Flags: review?(mstange) → review+
Comment 10•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox41:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
You need to log in
before you can comment on or make changes to this bug.
Description
•