surface largest_free_vm_block in crash report summary, make it searchable

NEW
Unassigned

Status

Socorro
General
2 years ago
2 years ago

People

(Reporter: froydnj, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

An OOM crash report, such as https://crash-stats.mozilla.com/report/index/e59d2f18-2131-4f24-9f43-7038b2160524, has stats like:

Total Virtual Memory 	

2147352576

Available Virtual Memory 	

122331136

It's not always obvious in an OOM crash why things should be falling over when there's a lot of virtual memory available.  largest_free_vm_block gives a better picture of the memory fragmentation, and would be useful to see in reports.  I thought we captured this, but I didn't know enough to look in the raw dump to find it.

I see there's also bug 939871 for being able to search on this field, which also seems useful.
largest_free_vm_block is already available in search, but I think as it is a sub key of the json dump, it won't be displayed in our Metadata tab. However, you can go to the Raw Dump tab and search for `largest_free_vm_block` to find the value.
You need to log in before you can comment on or make changes to this bug.