1720881 - Access to a memory dump to retrieve weeks of lost dev work (please!!)

Status: RESOLVED INCOMPLETE

(Socorro :: Data request, task)

Description

[kestas]

Attachment: Capture.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

I have lost some code that I spent a few weeks working on that I've lost in a server move. Tracing back through the file history I can see Firefox crashed right when I was in a development sprint (it was a WebGL Canvas page, and the crash refers to a WebGL2 canvas issue).

When I go to about:crashes and follow the link I can see that I sent diagnostic data, which I assume contains the source of the page I was rendering!!
https://crash-stats.mozilla.org/report/index/b0b1ff7f-e883-4cd3-bcf5-4e4e60210103

Is there any way I can get access to the memory dump for this crash? Please I'll gladly make a chunky donation in the name of whoever takes the time to help out another developer out!

Actual results:

Firefox crashed and sent a memory dump, possibly saving the only copy of some code I worked on for weeks.

Expected results:

I should have been more careful and taken backups .. But Firefox did exactly as it should and now crash-stats.mozilla.org is my only hope of retrieving this open source code I was working on.

Let me know what I can upload to prove that I am the person who uploaded the crash dump. Attached is a picture of how I arrived here.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Canvas: WebGL' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Mayank Bansal]

(In reply to kestas from comment #0)

Created attachment 9231554 [details]
Capture.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

I have lost some code that I spent a few weeks working on that I've lost in a server move. Tracing back through the file history I can see Firefox crashed right when I was in a development sprint (it was a WebGL Canvas page, and the crash refers to a WebGL2 canvas issue).

When I go to about:crashes and follow the link I can see that I sent diagnostic data, which I assume contains the source of the page I was rendering!!
https://crash-stats.mozilla.org/report/index/b0b1ff7f-e883-4cd3-bcf5-4e4e60210103

Is there any way I can get access to the memory dump for this crash? Please I'll gladly make a chunky donation in the name of whoever takes the time to help out another developer out!

Actual results:

Firefox crashed and sent a memory dump, possibly saving the only copy of some code I worked on for weeks.

Expected results:

I should have been more careful and taken backups .. But Firefox did exactly as it should and now crash-stats.mozilla.org is my only hope of retrieving this open source code I was working on.

Let me know what I can upload to prove that I am the person who uploaded the crash dump. Attached is a picture of how I arrived here.

Cash dumps created from about:crashes do not contain source code of the page. Im sorry that you lost your data, but Mozilla will not be able to help you get your data back.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

I'm switching this over to Socorro :: Data Request since that's what this is.

kestas: I don't think we can help. The minidump that gets sent in the crash report is a minimal core dump that contains contents of registers, some details about threads and the process, and the stack as a list of memory addresses. It has a little bit of memory, but won't cover the data you're looking for since it's not a full core dump.

I don't know what other options you have for retrieving the data. I'm really sorry.

Comment 4

[kestas]

Dang, that's a shame .. Oh well it was a long shot.

Comment 5

[Gabriele Svelto [:gsvelto]]

FYI I had a look at the crash report and as Will said there's nothing of value in it. We strive to catch as little user data as possible in a crash reporter so that's that, sorry we couldn't help.