STR 1. load https://crash-stats.mozilla.com/search/ 2. Choose "dump" - "contains" in the first two form fields 3. paste nsStyleTableBorder::Destroy in the value field, followed by RETURN 4. click Search ACTUAL RESULTS "No results were found." (see URL field for the actual URL that resulted from the steps above) Now look at: bp-f455320e-feb1-44a1-b2d1-8549b2141111 It's two days old and has nsStyleTableBorder::Destroy in stack Frame 1. Why did this crash report not match the query? Am I doing something wrong? I'm trying to find crash reports that has a certain string in any of the stack frames, not just the top one.
That sounds like a bug we had quite some time ago. Either that bug is still open and we haven't fixed it or this is a new issue because of the switch from pipe dumps to JSOM dumps?
Bug 480503 comment 40 claims it was fixed.
As KaiRo stated this is no dupe, the `dump` simply doesn't exist anymore in our crash reports. I need to enable the new json-dump in Super Search, but that's more easily said than done. Working on it!
Assignee: nobody → adrian
Status: NEW → ASSIGNED
Priority: -- → P1
Summary: Can't search for stack frames beyond the top frame in socorro → Enable the json-dump field in Super Search and remove the now deprecated dump field
It is impossible to just "enable the JSON dump", because it's a complex object containing a lot of things. What is possible instead, is to enable the specific fields that you need inside the JSON dump. Some are already accessible (namely `tiny_block_size` and `write_combine_size`). So, what I would need is a list of the fields that should be added. It doesn't need to be exhaustive, because it's now very easy to add new fields to Super Search (any superuser can do it, there's a guide here: http://adrian.gaudebert.fr/blog/post/2014/12/02/socorro-super-search-fields-guide ).
The original problem summary was "Can't search for stack frames beyond the top frame in socorro". So, please add whatever fields are necessary to do that. Thanks.
Solutions to this problem are difficult to come by, but spectateur  is a start. I'm lowering the priority a little, but rest assured I keep this in mind.  http://spectateur.mozilla.io/
Priority: P1 → P2
So we have a bit of the JSON dump in now, but just a tiny bit. At the moment, we do not plan on adding any more, and instead will be relying on the data being stored and accessible in Telemetry. Consequently, I am marking this as WONTFIX.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.