Closed Bug 712441 Opened 11 years ago Closed 11 years ago

How do startup crashes in js::Shape::finalize correlate with addon usage

Categories

(Mozilla Metrics :: Hadoop/HBase Operations, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Unreviewed

People

(Reporter: cww, Assigned: rhelmer)

Details

Attachments

(3 files, 1 obsolete file)

We're looking at js::Shape::finalize (and js::Shape::removeChild )

https://bugzilla.mozilla.org/show_bug.cgi?id=711794

We want to know how many of the startup (<60s uptime) crashes with the above signature come from users with no add-ons (as a percentage)?

(There may be a followup question here too.)
Group: mozilla-corporation-confidential
We don't have info on addons in the DB Socorro uses, but I believe that this is in HBase.
Assignee: nobody → tmeyarivan
Group: mozilla-corporation-confidential → metrics-private
Component: Socorro → Hadoop/HBase Operations
Product: Webtools → Mozilla Metrics
QA Contact: socorro → hadoop-cluster
Version: Trunk → unspecified
Assignee: tmeyarivan → nobody
Component: Hadoop/HBase Operations → Data/Backend Reports
QA Contact: hadoop-cluster → data-reports
I just checked and see this in the JSON that is stored in HBase e.g.:
https://crash-stats.mozilla.com/dumps/446e67d0-def4-43e7-8228-7d62e2110316.jsonz
contains
"addons": [["{972ce4c6-7e08-4474-a285-3208198ce6fd}", "4.0b13pre"], ["xulapp@toolness.com", "1.0"]]
Component: Data/Backend Reports → Hadoop/HBase Operations
Severity: normal → critical
Component: Hadoop/HBase Operations → Data/Backend Reports
I am able to do this using the DB and pulling the JSON via thrift. If someone else if already on this let me know, I got the basic info for this and am now looking into another question about the data (details forthcoming).
Assignee: nobody → rhelmer
Severity: critical → normal
Component: Data/Backend Reports → Hadoop/HBase Operations
Using this query against prod Socorro DB:

SELECT uuid FROM reportsWHERE signature = 'js::Shape::finalize'  
OR signature = 'js::Shape::removeChild' 
AND uptime < 60

I get 1671 total.

Ran a script to extract individual crashes based on this list of crash IDs, here are the results:

47 of 1671 (0.028%) have no addons.

Cww also provided a list of "bad addons" to check against:
http://pastebin.mozilla.org/1413927

9 of 1671 (0.005%0 contain an addon from the "bad" list.

We added the addon ID {841468a1-d7f4-4bd3-84e6-bb0f13a06c64} to the "bad" list to sanity check:

175 of 1671 (0.1%) contain the addon ID {841468a1-d7f4-4bd3-84e6-bb0f13a06c64}
Assignee: rhelmer → nobody
Severity: normal → critical
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
Attached file list of "bad" addons
Attached file list of crash IDs checked (obsolete) —
List of crash IDs checked for comment 4
There is nothing private in this post (uses publicly available data).
Group: metrics-private
(In reply to Robert Helmer [:rhelmer] from comment #4)
> Using this query against prod Socorro DB:
> 
> SELECT uuid FROM reports WHERE signature = 'js::Shape::finalize'  
> OR signature = 'js::Shape::removeChild' 
> AND uptime < 60
> 
> I get 1671 total.

Actually the operator precedence is a little off here, this is binding as "WHERE a OR (b AND c)" when we want "WHERE (a OR b) AND c". The original run had this but it got dropped along the way, sorry about that.

This query should be:

SELECT uuid FROM reports
WHERE (signature = 'js::Shape::finalize'  OR signature = 'js::Shape::removeChild')
AND uptime < 60

It does not really change the outcome:

total: 1174
no addons: 9 of 1174 (0.008%)
"bad" addons: 8 of 1174 (0.007%)
Attachment #583337 - Attachment is obsolete: true
(In reply to Robert Helmer [:rhelmer] from comment #4)
> 175 of 1671 (0.1%) contain the addon ID
> {841468a1-d7f4-4bd3-84e6-bb0f13a06c64}

With the revised query from comment 9 this is:

171 of 1174 (0.15%) contain the addon ID {841468a1-d7f4-4bd3-84e6-bb0f13a06c64}
Severity: critical → normal
Status: ASSIGNED → NEW
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.