Bugzilla

This is super helpful!

I looked at the code. We've already got a processor rule that creates a `process_type` field, so I'm going to reuse that. It'll do:

1. if there's a ProcessType annotation, then use that
2. if there's no ProcessType annotation, then use "parent"

Thus the changes for this bug will be:

1. change the processor rules so we have one that creates a `process_type` field in the processed crash that defaults to "parent"
2. add "parent" to all the hard-coded places we have process types
3. write up a new bug to remove the hard-coded process types and all the "browser" means "does not exist" nonsense and schedule that work for 3 months from now

This is super helpful!

I looked at the code. We've already got a processor rule that creates a `process_type` field, so I'm going to reuse that. It'll do:

1. if there's a ProcessType annotation, then use that
2. if there's no ProcessType annotation, then use "parent"

Thus the changes for this bug will be:

1. change the processor rules so we have one that creates a `process_type` field in the processed crash that defaults to "parent" -- this will cause it to show up in the Details tab going forward
2. add "parent" to all the hard-coded places we have process types
3. write up a new bug to remove the hard-coded process types and all the "browser" means "does not exist" nonsense and schedule that work for 3 months from now