Closed Bug 1133365 Opened 11 years ago Closed 11 years ago

determine whether DXVA is running in a crash report

Categories

(Socorro :: Data request, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lonnen, Assigned: adrian)

Details

We're looking to sample a few hundred crashes from the following signatures for Firefox 36 Beta: moz_abort | pages_commit D2DDeviceContextBase<ID2D1DeviceContext1, ID2D1DeviceContext1, null_type>::FillRectangle(D2D_RECT_F const*, ID2D1Brush*) DrawingContext::FillRectangle(D2D_RECT_F const*, ID2D1Brush*) for each crash we want to sort them into one of three buckets using the following criteria: if (no threads in msmpeg2vdec.dll) => Not playing video else if (appnote contains "D3D9Layers") if (1 or fewer threads in d3d9.dll) => Playing video without DXVA else => Playing video with DXVA else if (1 or more threads in d3d9.dll) => Playing video with DXVA else => Playing video without DXVA
I was able to grab UUID's with the following URL and a bit of python: https://crash-stats.mozilla.com/api/SuperSearch/?product={PRODUCT}&version={VERSION}&signature={SIGNATURE}&results_number={SAMPLE_SIZE} crashes = requests.get(url.format(**opts)).json()['hits'] uuids = [crash['uuid'] for crash in crashes] but I couldn't figure out how to get the crashing threads from the UUIDs in python. I can grab them one at a time but we're looking at a hew hundred of these, minimum, so programmatic access is best.
The thread list and module list is at ProcessedCrash.json_dump.threads
Assignee: nobody → adrian
OS: Mac OS X → All
Priority: -- → P1
Hardware: x86 → All
Here comes the data! Hopefully the script I have written is correct, if not let me know and I can rerun it with corrections. If this is what you were expecting, please mark this bug as resolved! :-) Script ====== https://gist.github.com/AdrianGaudebert/c05a8f7bd13fec9b7701 Note: this script uses SuperSearchUnredacted, which requires several permissions to be accessible. If you want to run it yourself, you'll have to get a Token from crashstats [0] and make sure you have the following permissions: view_pii and view_expoitability. (Sadly, bug 1136145 prevented me from exposing the json_dump in Super Search, and I thus have not been able to do this with Spectateur [1]. :( ) [0] https://crash-stats.mozilla.com/api/tokens/ [1] https://spectateur.herokuapp.com/ Data ==== 500 results were processed per signature, taken randomly across the last 2 weeks of data on production. In parentheses, the number of processed results and the total number of results for that signature. > moz_abort | pages_commit (500 / 4507) > ------------------------------------- > > DXVA off 1 > DXVA on 13 > no video 486 > > D2DDeviceContextBase<ID2D1DeviceContext1, ID2D1DeviceContext1, null_type>::FillRectangle(D2D_RECT_F const*, ID2D1Brush*) (500 / 3633) > ------------------------------------------------------------------------------------------------------------------------------------- > > DXVA off 0 > DXVA on 46 > no video 454 > > DrawingContext::FillRectangle(D2D_RECT_F const*, ID2D1Brush*) (500 / 1688) > -------------------------------------------------------------------------- > > DXVA off 1 > DXVA on 37 > no video 462
I now realize that I forgot to enforce the crashes being in a beta (I only added version=36.0). Should I rerun that with release_channel=beta?
> 15:43 <bsmedberg> bug 1133365 is ajones/cpearce and maybe some others CC'ing those who should be interested in this bug. :-)
> 15:51 <bsmedberg> adrian: oh also Bas for DXVA Sorry for the spam!
In the absence of answers here, I'm going to mark it as resolved. Please reopen if you need more data from me!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.