Closed Bug 667030 Opened 9 years ago Closed 8 years ago

Possibility to search for content crashes


(Socorro :: General, task)

Not set


(Not tracked)



(Reporter: kairo, Assigned: lonnen)



(Whiteboard: Q42011wanted)

Fennec already lists content crashes, and Firefox will get those as well some time, hopefully later this year. (Bug 578687 also talks about jetpack processes, but I have no clue on the plans there right now, let's keep in mind that those might come as well and build stuff in a way so those can be added easily.)

A first step to improving support for those would be to be able to search for process_type=content from advanced search.
Target Milestone: --- → 2.3.1
Target Milestone: 2.3.1 → 2.3.2
Whiteboard: Q42011wanted
This should go into 2.3.3, but we don't have a 2.3.3 yet.
Assignee: nobody → chris.lonnen
By which I mean "retriage at that stage" - may be done with ES, maybe with reports_clean, or maybe with newtcbs.
Spun off the elastic search as an implementation in a separate bug, which is blocking the tracker for content crashes but shouldn't block this.

adrian: r?
See Also: → 698121
The number problem that I saw yesterday was explained to me by jberkus: it's due to search counting unique signatures, so if 2 crashes with the same signature have different process types, that signature will appear in both types but will be counted only once in "any". 

r+ and merged.
Commit pushed to
Merge pull request #117 from Lonnen/667030-search

add content as a recognized option in the postgres implementation, add a 
Fixes bug 667030
Closed: 8 years ago
Resolution: --- → FIXED
I am very sorry I merged something that is not fully working. I forgot to test the topcrashers part as there was a change there too. When I hit the "content" type link I get that error:
Resolution: FIXED → ---
The config change was already committed here:

It was accidentally also included in the pull request I asked you to review.

The error occurs because the middleware relies on an additional function that isn't in your dump of the db yet. You can put it there by running the contents of ( in your psql shell. After that, it should work fine.
Since this is working on dev ( I'm going to re-mark it as fixed. Adrian, please re-open if you run the migration script and get the same error.
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
QA verified. Content crashes are viewable.
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.