835491 - Is it possible to attach a file to a crash report?

Status: RESOLVED WONTFIX

(Socorro :: General, task)

Description

[Håkon Løvdal]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130109165101

Steps to reproduce:

I would like to attach a file to an automatic crash report, https://crash-stats.mozilla.com/report/index/bp-68ffd846-d86f-4e64-84cd-00a7d2130122. The reason for this is that the ~/.mozilla directory was at time of the crash as clean and pure as it gets, containing nothing but a default install + installation of extensions, when it crashed on the first site I visited. I tared the whole directory (just 18Mb) and I expect that it could contain useful information in determining why firefox crashed (and it is chemical free of any personal information so there is no problem in sharing all of it).



Expected results:

However, at crash-stats.mozilla.com there are no possibilities for attaching files. Maybe this is by design because everything there is only processed by tools and humans more or less never interact directly with the reports. Should I create a new bug report for the crash here on bugzilla.mozilla.org? I'll attach the file to this bug report as well, to let you have a look at it.

Comment 1

[Robert Kaiser]

For one thing, stuff like that would belong into a bug report and not the crash report - we're already e.g. not using a full core dump but a "minidump" because we don't want crash reports to be multi-megabyte. We are collecting multiple millions of reports per day, the storage requirements would be huge if every report was "just 18MB".

That said, esp. if this profile is as pristine as you say, it would be pretty useless for us to analyze, as it can't contain a lot of interesting stuff when it's clean. We e.g. already have the list of your active add-ons in the report.

What would be more useful is e.g. if it happens without add-ons (e.g. in "safe mode" or with them disabled) as well, or if it happens in a build downloaded from Mozilla as well (yours is some variant/version that apparently hasn't been compiled by us or one of our partners, because we are missing "symbol" information that would give us a clue where in the code the crash happens).

So, the original request to attach a file to a crash report in this way is "invalid" in our terms of speaking, but your crash itself could be worth working through if you clear up some questions like those above.

Comment 2

[Håkon Løvdal]

Well, in case anyone is interested, the file is at http://www.filetolink.com/f524f59b0d. The firefox version was a stock Fedora firefox-18.0-1.fc18. I only had one crash but I will see it I can reproduce with the official version.

Comment 3

[Håkon Løvdal]

I did manage to reproduce running the official mozilla binary (firefox-18.0.1.tar.bz2, running "./run-mozilla.sh firefox"), https://crash-stats.mozilla.com/report/index/bp-5a4d4ba9-c9a8-4036-879f-9120c2130128. Should I create a new bug rather than continue commenting on this one? Or would one of you create one and inform me?

Comment 4

[Benjamin Smedberg]

Yes, if there is a crash that you can reproduce, please file a bug in the proper Core/Firefox component; it would be confusing to morph this bug.