I'd like to take the equivalent of this set of crash reports and get the OOMAllocationSize for them: https://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox%3A13.0.1&version=Firefox%3A13.0&query_search=signature&query_type=contains&query=nsSegmentedBuffer%3A%3AAppendNewSegment&reason_type=contains&date=06%2F19%2F2012%2018%3A29%3A56&range_value=1&range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=mozalloc_abort%28char%20const*%20const%29%20|%20mozalloc_handle_oom%28unsigned%20int%29%20|%20moz_xmalloc%20|%20nsSegmentedBuffer%3A%3AAppendNewSegment%28%29 that is: Firefox 13.0.1, past week or so, with a signature of "mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | nsSegmentedBuffer::AppendNewSegment()" In the summary it is sufficient to include just the ID and the OOMAllocationSize, but if it's relatively easy to also include the "Available Virtual Memory", "Available Physical Memory", "Available Page File" numbers, that would be an awesome bonus.
Created attachment 634543 [details] script used to pull raw crash data Just for reference, here's the script I used. crash_ids were gathered using: psql -U $databaseUserName -h $databaseHost $databaseName -c "copy ( select uuid from reports where version='13.0.1' and product='Firefox' and signature = 'mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | nsSegmentedBuffer::AppendNewSegment()' and date_processed > (CURRENT_DATE - INTERVAL '7 days')) to stdout with csv"
Attachment #634543 - Attachment mime type: text/x-python-script → text/plain
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Attachment #634544 - Attachment mime type: text/csv → text/plain
You need to log in before you can comment on or make changes to this bug.