For Mac: 1. go to : https://crash-stats.mozilla.com/report/index/bp-b775be3d-b6bc-490a-b61f-211b62110816 2. look at app notes 3. look at about:support and the graphics section Adapter Description0x22600,0x20400WebGL RendererNVIDIA Corporation -- NVIDIA GeForce GT 330M OpenGL Engine -- 2.1 NVIDIA-1.6.36GPU Accelerated Windows27/27 OpenGL Expected: there shouldn't be a discrepancy Actual: there is a discrepancy For Android: Example 1: https://crash-stats.mozilla.com/report/index/daad30b2-fa34-4aec-98c5-5bb5c2110921 example here shows : asus Transformer TF101 asus/US_epad/TF101:3.2/HTJ85B/US_epad-22.214.171.124-20110816:user/release-keys Example 2: http://crash-stats.mozilla.com/report/index/167c7ef1-88ca-4cb9-8242-a51562110727 where it states : Process Notes aren't listed because they're too long This was on my own toshiba thrive. Example 3: https://crash-stats.mozilla.com/report/index/bp-6f729417-73ca-4c32-9706-dbfd82110901 third example is does not even show the App notes section Note: This might need to move to the breakpad instead of soccorro?
I think it actually belongs in GFX, not in either Breakpad or Socorro. Benoit?
(In reply to Naoki Hirata :nhirata from comment #0) > For Mac: > > 1. go to : > https://crash-stats.mozilla.com/report/index/bp-b775be3d-b6bc-490a-b61f- > 211b62110816 > 2. look at app notes > 3. look at about:support and the graphics section > Adapter Description0x22600,0x20400WebGL RendererNVIDIA Corporation -- NVIDIA > GeForce GT 330M OpenGL Engine -- 2.1 NVIDIA-1.6.36GPU Accelerated > Windows27/27 OpenGL > > Expected: there shouldn't be a discrepancy > Actual: there is a discrepancy What discrepancy do you see at this point? The discrepancy that I can see is that while Desktop Firefox crash reports report Graphics information, Fennec crash reports don't. If this is what this bug is about, then I confirm that this should move to Core:Graphics.
7 years ago
Component: Socorro → Graphics
Product: Webtools → Core
QA Contact: socorro → thebes
Moved to Core Graphics based on Comment 2
You need to log in before you can comment on or make changes to this bug.