Closed
Bug 712824
Opened 13 years ago
Closed 12 years ago
Query for instances where Firefox version does not match Default Extension ID version
Categories
(Socorro :: Data request, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: marcia, Assigned: aphadke)
Details
(Whiteboard: ETA: 1/12)
Attachments
(1 file)
(deleted),
application/zip
|
Details |
https://crash-stats.mozilla.com/report/index/5ac492ee-1f64-49e3-8abf-512e62111221. This crash report is strange in that it reports a Firefox version of 9.0, but a default Firefox extension version of 8.0.1. I have not seen this before while reviewing crash stats. AFAIK they should match.
Wondering what is causing this mismatch and how widespread it is.
Is there a way to construct a query that would catch other instances of this - both 9.0 Firefox version/Extension ID Version {972ce4c6-7e08-4474-a285-3208198ce6fd} 8.0.1 as well as similar mismatches that may appear in other releases?
Reporter | ||
Comment 1•13 years ago
|
||
Adding Alex and Christian in case they have seen anything like this in the past.
I have a vague recollection about something like this. Adding rs as he looked into the frankenfoxes with me last time and may have a better memory
Reporter | ||
Comment 3•13 years ago
|
||
Note that the crashes that showed this behavior were Mac crashes, not Windows.
Comment 4•13 years ago
|
||
We didn't get the default theme's version in the Windows reports.
Anurag, would you be able to create this report. I'd like it to just have Firefox version, the version for extension id {972ce4c6-7e08-4474-a285-3208198ce6fd}, last crash, install age, and uptime across all platforms.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → aphadke
Assignee | ||
Comment 5•13 years ago
|
||
> Anurag, would you be able to create this report. I'd like it to just have
> Firefox version, the version for extension id
> {972ce4c6-7e08-4474-a285-3208198ce6fd}, last crash, install age, and uptime
> across all platforms.
:rstrong - what time range? past 6 months or less?
Whiteboard: ETA: 1/8
Comment 6•13 years ago
|
||
I think 3 months would be adequate for the initial investigation so we can see whether this is a significant issue.
Assignee | ||
Comment 7•13 years ago
|
||
:rstrong
Got two questions for you:
1. We have about 100k crashes per day. How do you want to sort this data? raw-dump, group by Fx version, etc.?
2. Some of the crashes don't have uptime or install_age (see below), the respective columns would be blank in the final report.
Sample data from 12/21 to 12/22 below, the final run will have it tab separated with row headings etc. (last column is the unique count, ignore that for now)
ooid: f3c06d33-4b53-4236-9412-37b672111222 ExtensionIdVersion: 7.0 FxVersion: 8.0 secondsSinceLastCrash:333915 uptime: 38434 install_age: 3724710 1
ooid: f3d81eab-4bb9-4a10-827d-7872c2111221 ExtensionIdVersion: 8.0 FxVersion: 9.0 secondsSinceLastCrash:70 1
ooid: f3de72f9-2447-4dab-9d77-d9d852111222 ExtensionIdVersion: 6.0.2 FxVersion: 8.0 secondsSinceLastCrash:2142 1
ooid: f3f7344c-206e-4561-9312-c31202111222 ExtensionIdVersion: 5.0 FxVersion: 8.0 secondsSinceLastCrash:6 1
ooid: f40054fa-367d-43fd-a6c6-edd012111222 ExtensionIdVersion: 8.0.1 FxVersion: 9.0.1 secondsSinceLastCrash:91 1
ooid: f40bea24-ee5c-4958-b42b-5a32a2111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:28201 1
ooid: f41c26af-ce19-4d0a-875f-de08e2111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:180134 1
ooid: f423af95-7d68-4c07-a3fe-330492111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:994 1
ooid: f425ad9a-1a96-4e83-a6cc-27e882111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:1126124 1
ooid: f42a9a81-ec64-49d0-976e-69a422111221 ExtensionIdVersion: 8.0.1 FxVersion: 8.0 secondsSinceLastCrash:2972 1
ooid: f440ac13-978f-4f56-8ea9-31a8a2111221 ExtensionIdVersion: 6.0.2 FxVersion: 8.0 secondsSinceLastCrash:80544 1
ooid: f445c6da-fb3d-4a19-8400-c3d772111222 ExtensionIdVersion: 8.0 FxVersion: 8.0.1 secondsSinceLastCrash:784096 1
ooid: f44e51e1-e922-4b71-969a-0b5782111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:null 1
ooid: f458b936-6f03-4dd4-8f77-b8b842111222 ExtensionIdVersion: 8.0.1 FxVersion: 9.0.1 secondsSinceLastCrash:975 1
ooid: f471b038-0f80-4ce8-80e4-4db4e2111221 ExtensionIdVersion: 6.0.2 FxVersion: 8.0.1 secondsSinceLastCrash:null 1
ooid: f48cee37-71ba-40ec-b918-e3ab22111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:null 1
ooid: f4a5f5b9-9c76-4bd6-9ad7-7e6c32111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:352 1
ooid: f4b47a39-e08e-41e7-b3e8-4b5cd2111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:260668 1
ooid: f4b6407b-b50a-426b-b4f0-c9caa2111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:null 1
ooid: f4b947fb-669f-4171-9c9a-023342111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:null 1
ooid: f4d3fb3d-22cf-4a9d-a98d-73e492111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:null 1
ooid: f4ee9b5c-b64e-4fb0-9703-c4e3c2111221 ExtensionIdVersion: 8.0 FxVersion: 9.0 secondsSinceLastCrash:7 1
ooid: f4f07a58-ca43-4a46-9f04-8658d2111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0 secondsSinceLastCrash:null 1
ooid: f4f84099-b5cb-4d97-9cb0-dc4512111222 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:3614 1
ooid: f4fb7c6f-78b7-4496-b31b-cc7fe2111221 ExtensionIdVersion: 5.0 FxVersion: 8.0 secondsSinceLastCrash:66478 1
ooid: f5016256-4703-41ae-b720-1eee22111221 ExtensionIdVersion: 7.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:null 1
ooid: f508b7e8-8df3-4813-b000-dd6d72111222 ExtensionIdVersion: 5.0.1 FxVersion: 8.0.1 secondsSinceLastCrash:null uptime: 4738 install_age: 47854 1
ooid: f522e30d-8948-4ff7-8ae9-464e02111221 ExtensionIdVersion: 3.6.24 FxVersion: 3.6.23 secondsSinceLastCrash:45 1
ooid: f53b47c9-bae2-46f8-af0c-a60d52111221 ExtensionIdVersion: 8.0 FxVersion: 9.0 secondsSinceLastCrash:3774 uptime: 3310 install_age: 420589 1
Reporter | ||
Comment 8•13 years ago
|
||
https://crash-stats.mozilla.com/report/index/d46619da-85cc-4291-8b1e-4590b2120102 was another instance of this I see in looking at 10.0 beta stuff.
Comment 9•13 years ago
|
||
The files in the modules list have the correct version number. This might very well be due to the add-ons manager not updating the metadata or the crashreporter values for the default theme.
Comment 10•13 years ago
|
||
(In reply to aphadke from comment #7)
> :rstrong
> Got two questions for you:
>
> 1. We have about 100k crashes per day. How do you want to sort this data?
> raw-dump, group by Fx version, etc.?
raw dump with no grouping
> 2. Some of the crashes don't have uptime or install_age (see below), the
> respective columns would be blank in the final report.
That's perfect
>
> Sample data from 12/21 to 12/22 below, the final run will have it tab
> separated with row headings etc. (last column is the unique count, ignore
> that for now)
What is the unique count? I would prefer not to have anything summed / counted.
Assignee | ||
Comment 11•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Whiteboard: ETA: 1/8 → ETA: 1/12
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•