Is there a reason you need permissions for the memory report? Don't we anonymize it?
-e On Mon, Oct 10, 2016 at 8:34 AM, Benjamin Smedberg <benja...@smedbergs.us> wrote: > Yes, downloading raw minidumps and memory reports requires the PII > permission in crash-stats. This can be obtained by Mozilla employees with > the assent of your manager, although I'm not sure now what the correct > bugzilla component is. > > --BDS > > On Mon, Oct 10, 2016 at 6:23 PM, Ben Kelly <bke...@mozilla.com> wrote: > > > Does the "raw dump" tab support require special permissions? I don't see > > any way to download the memory report from: > > > > https://crash-stats.mozilla.com/report/index/1a572047- > > ac64-4add-a82f-a31512161004#tab-rawdump > > > > On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote < > > n.netherc...@gmail.com> > > wrote: > > > > > Greetings, > > > > > > crash-stats.mozilla.org has had some recent improvements that are > > > worth highlighting. > > > > > > - There is new documentation on how to search through crash reports: > > > https://developer.mozilla.org/en-US/docs/A_guide_to_ > > > searching_crash_reports. > > > You might think you already know how to do this, but crash-stats' > > > functionality for *grouping* search results is powerful and easy to > > > overlook, so this page is worth reading to make sure you understand it > > > fully. This documentation is linked to from the Super Search page > > > within crash-stats. > > > > > > - Some crash reports contain memory reports. (The > > > "ContainsMemoryReport" field is set in that case.) It used to be > > > difficult to download this memory report, but thanks to Peter > > > Bengtsson it's now much easier -- when a memory report is present, > > > there's now a link to it from the "Raw Dump" tab of an individual > > > crash report. See > > > https://crash-stats.mozilla.com/report/index/1a572047- > > > ac64-4add-a82f-a31512161004#tab-rawdump > > > for an example. > > > > > > - Also, something that is not in crash-stats but is closely related: > > > Marco Castellucio's new crash tools at > > > https://mozilla.github.io/stab-crashes/. There are several tools, but > > > probably the most widely-applicable one is > > > https://mozilla.github.io/stab-crashes/correlations.html, which finds > > > correlations for a particular crash signature. It works much better > > > than the existing correlations tool within crash-stats. If you have a > > > crash for which the cause is not obvious, this tool can be enormously > > > helpful -- e.g. bug 1307029 is for a generic-looking crash signature > > > that turns out to be highly correlated with a particular extension. > > > > > > Nick > > > _______________________________________________ > > > dev-platform mailing list > > > dev-platform@lists.mozilla.org > > > https://lists.mozilla.org/listinfo/dev-platform > > > > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
