671899 - Socorro - add support for 'content' crashes in the UI

Status: VERIFIED FIXED

(Socorro :: General, task)

Comment 1

[Laura Thomson :laura]

Audit to make sure these are getting included in searches and aggregates.  We already know of one problem in bug 667033.

Comment 2

[Lonnen :lonnen]

Add icons to top crashers tables representing a content crash

Comment 3

[Lonnen :lonnen]

The graph data ultimately comes from the aduByDay web service call, which explicitly defines "report-type": 'any' to mean browser crashes and normalized hangs. It ignores the three other crash types.

Comment 4

[Robert Kaiser]

If possible, we'll also want TCBS for content crashes (just like we do for plugin and browser crashes), not sure if that already has its own bug.

Comment 5

[Robert Kaiser]

(In reply to comment #2)
> Add icons to top crashers tables representing a content crash

Bug 580715 has done that. :)

Comment 6

[Lonnen :lonnen]

580715 created the icons, but they are not in the repository and there is no code for displaying them in the top crashers tables.

Comment 7

[Lonnen :lonnen]

Adding content crash icons will require changes to TCBS. It will have to wait until the dust settles on 664182. We've verified content crashes are being counted in the current tcbs implementation, they just won't have an icon to indicate where they are.

I can also confirm that they are in the reports table, and the daily_crashes table. The postgres search implementation queries against reports. Following the changes to 667033 content crashes are being counted in the UI.

Comment 8

[Lonnen :lonnen]

pull req and merge: https://github.com/mozilla/socorro/pull/118

Comment 9

[Matt Brandt [:mbrandt]]

(In reply to Chris Lonnen :lonnen from comment #7)
> I can also confirm that they are in the reports table, and the daily_crashes
> table. The postgres search implementation queries against reports. Following
> the changes to 667033 content crashes are being counted in the UI.
I can confirm this as well. QA verified.