1061960 - Allow loading about:memory data from a crash report back into the about:memory viewer

Status: RESOLVED FIXED

(Toolkit :: about:memory, defect)

Description

[Benjamin Smedberg]

Crash reports can now contain about:memory data! dmajor would like an easy way to load this into the about:memory viewer, and filed bug 1061371, but I think it might be even easier to just load the data directly from the crash-stats API for display.

e.g. https://crash-stats.mozilla.com/api/ProcessedCrash/?crash_id=a3b212d7-505f-44c7-8f62-0d41b2140831&datatype=processed the "memory_info" key in the root object has the about:memory data.

njn do you have somebody who can whip this up?

Comment 1

[Nicholas Nethercote [inactive]]

> njn do you have somebody who can whip this up?

Hmm, if anyone, it would probably be me. I might be able to but my webdev skills aren't great.
This is similar to bug 859603. What would the UI be like -- have a text box where you can paste a URL, and then a button next to it that says "Load from URL"?

> https://crash-stats.mozilla.com/api/ProcessedCrash/?crash_id=a3b212d7-505f-
> 44c7-8f62-0d41b2140831&datatype=processed the "memory_info" key in the root
> object has the about:memory data.

I can't find "memory_info" anywhere in that page. Is that the right link?

Comment 2

[(Away)]

It's "memory_report" but it only shows up if you have the right access bits. It would look like:

[...]
"reason": "EXCEPTION_BREAKPOINT", 
"memory_report": {
"version": 1, 
[...]
}, 
"completeddatetime": "2014-08-31 21:15:03.980248", 
[...]

Comment 3

[(Away)]

I wouldn't have a huge text box taking up space when most people don't need it. Maybe make something appear after clicking a button? Do we still support prompt()? Then again my webdev skills are circa 1995, maybe you shouldn't listen to me :)

Comment 4

[Nicholas Nethercote [inactive]]

(In reply to David Major [:dmajor] from comment #2)
> It's "memory_report" but it only shows up if you have the right access bits.
> It would look like:
> 
> [...]
> "reason": "EXCEPTION_BREAKPOINT", 
> "memory_report": {
> "version": 1, 
> [...]
> }, 
> "completeddatetime": "2014-08-31 21:15:03.980248", 
> [...]

Ah. I guess I'll need access, then. I filed bug 1062070.

> I wouldn't have a huge text box taking up space when most people don't need it.

I'll probably implement bug 859603 at the same time, which will make the textbox more widely useful. And I can make it small.

Comment 5

[Nicholas Nethercote [inactive]]

I talked with Chris Lonnen and this sounds harder that it first seemed. Because the data is restricted, to access it programmatically (e.g. via an XHR) you need a token from https://crash-stats.mozilla.com/api/tokens/. Doable -- I guess you'd specify the token as well as the URL before triggering the load -- but a complication.

Also, not every crash is processed. If you request the report in the webapp we'll process it on demand and jump it to the front of the queue, but requesting via the API might not be enough.

Here's a first step that won't be quite as convenient but should be a lot better than the current situation: modify the "Load..." and "Load and diff..." buttons to handle the crash reports format. E.g. they'd extract the |memory_report| field if present. With that in place, you could save a crash report locally and then load it in about:memory. dmajor, what do you think about that?

Comment 6

[(Away)]

> Here's a first step that won't be quite as convenient but should be a lot
> better than the current situation: modify the "Load..." and "Load and
> diff..." buttons to handle the crash reports format. E.g. they'd extract the
> |memory_report| field if present. With that in place, you could save a crash
> report locally and then load it in about:memory. dmajor, what do you think
> about that?

I'd be totally fine with that.

Comment 7

[Nicholas Nethercote [inactive]]

Attachment: In about:memory, allow the loading of memory reports embedded in crash dumps

This is a simple change. Immediately after parsing the JSON, we check if there
is a |memory_report| property. If so, it's presumably a crash report, and so we
can extract and work with the |memory_report| property.

I added tests for the "Load..." and "Load and diff..." functions.

Comment 8

[Nicholas Nethercote [inactive]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/3de899a46769

Comment 9

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/3de899a46769