Add AsyncShutdownTimeout to super search



4 years ago
3 years ago


(Reporter: Yoric, Assigned: adrian)


Firefox Tracking Flags

(Not tracked)


We are starting to receive a number crashes annotated with an AsyncShutdownTimeout field. For these crashes, the useful information is generally (only) the contents of the AsyncShutdownTimeout. It would be very useful if we could filter by the contents of that field.

Comment 1

4 years ago
You need to specify which specific field to add, as "metadata" can already be searched, just not the piece you are interested in.

Also, we'll probably need more info about what kind of data there is in a field so we can index it correctly. From what I've seen, AsyncShutdownTimeout is in raw-crash and has some JSON contents.

Adrian, can you add it with the correct options? (I got confused by the amount of things one needs to select for that.)
Assignee: nobody → adrian
Summary: Need to search by metadata → Add AsyncShutdownTimeout to super search

Comment 2

4 years ago
I would indeed need to know what kind of data that field can contain, especially if it's JSON. Any examples of what we can expect there?
Flags: needinfo?(dteller)
The general format is

  phase: string,
  conditions: array of [
    name: string, // This is the most important piece of information
    state: either arbitrary JSON or the string "(none)",
    // Since FF 33
    lineNumber: number,
    filename: string,
    // In FF 34+, we will probably add
    stack: string

In many (but not all) cases, `state` will itself have the same format as AsyncShutdownTimeout itself.

Is that information sufficient?
Flags: needinfo?(dteller)


4 years ago
Depends on: 1013322

Comment 4

3 years ago
The mapping of this field needed a "full" version for the string operators to work correctly. I have changed it on both stage and production, but now need to enable the "Has full version" parameter once the new mapping starts being used (Dec 22, 2014).


3 years ago
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.