mmohrhard / crash Goto Github PK

Currently the link for the backtrace is always using the 5-2 target. See https://github.com/mmohrhard/crash/blob/master/django/crashreport/stats/static/stats/js/details.js#L26

We should instead take the version entry and use the correct version string dynamically.

The only problem is around something like 5.3.0.0 which maps to 5-3 and not 5-3-0.

https://docs.djangoproject.com/en/1.9/topics/migrations/#version-control

See https://wiki.mozilla.org/Breakpad:Symbols#Windows_system_symbols for some information about that.

Add adjustable time ranges for the main view. Suggestion:

• 3 days
• 7 days (default)
• 14 days
• 30 days (one month)

To get an idea, attached you find how mozilla solved this for firefox crash stats.

This should come useful, since it allows to get a quick overview of how versions and crashes evolve.

The main page is really ugly right now and needs some love to improve the look.

Additionally the chart needs to be improved to make it more usable and fix a number of issues.

After uploading system symbols the missing symbol entries for uploaded symbols should be removed.

This allows us for example to support daily builds.

It would be very useful, to reflect if a bug is already fixed or still unfixed.

Suggestion:

Fixed bugs: tdf#100681 should be strikethrough
Unfixed: normal font

Currently there is no logging and I struggle a lot on the production machine to understand what is going on. Some information are written to the uwsgi log file but most information are just lost.

This requires to find a way to provide a good logging system and log errors that happen in the view.

dump_syms.exe can only handle with libraries that end in dll so just rename the file after download.

Currently the key-value pairs are hard coded. Change that in the upload form and in the model.

Currently we don't have a footer and we should fix that. There are at least some German legal requirements (Impressum) and the chance to make it look nicer.

Currently the chart data is added to the html page statically during the template generation. Ideally we would have a REST API that exposes the chart data and load it through an call. That would also remove the need to rerender on the server side after implementing issue #29.

For this to work we need to replace the code in https://github.com/mmohrhard/crash/blob/master/django/crashreport/stats/views.py#L82 and fix the TODO in https://github.com/mmohrhard/crash/blob/master/django/crashreport/stats/views.py#L94.

The corresponding change in the template is necessary in https://github.com/mmohrhard/crash/blob/master/django/crashreport/stats/templates/stats/main.html#L12 where we currently just store the data statically during template processing.

for example, the width_37 CSS class is missing from the generated and compressed CSS stylesheet, which messes up the headers, making the big green block at the top of the page take up waaaaaay more space than it should

Just filed tdf#105097 via the http://crashreport.libreoffice.org instance, but the bug report is not being picked up on the "Bugs" tab of the UI. I know I've seen linkages to bugs in past use of the service--has something broken?

=-ref-=
http://crashreport.libreoffice.org/stats/signature/ScTransferObj::~ScTransferObj()?page=1

We should compile our own minidump_stackwalk tool and enable the exploitability check in there. This is e.g. done by socorro but also requires to store that in the model.

Currently it is really difficult to setup the testing instance. It is not trivial to generate the necessary crash reports and the DB. There should be a number of scripts, an example database and anything else necessary to automatically setup a test instance.

although OS X is hated, having info about crash volumes for LO running on that OS would be highly valuable information. let's add OS X crash reporting. please? <3

The LibreOffice versions in the Version selector should be sorted.

I see there's MPL headers in some source files, adding a copying of the license in the main dir will make it clear.

It would be interesting if, in addition to the absolute number of crashes, you could also see the relative numbers (relative to the installations of libreoffice) in the diagram. This would provide a good indicator of the stability of a version.

Example: http://crashreport.libreoffice.org/stats/signature/com::sun::star::datatransfer::DataFormatTranslator::create(com::sun::star::uno::Reference%3Ccom::sun::star::uno::XComponentContext%3E%20const%20&)

Suggestions:

1. sort Date from latest to oldest by default (so the opposite of the current),
2. add sorters at for Date and Version columns,
3. add more convenient pagination to bottom (for example, move to first page, move 5 pages back, move to previous page, move to next page, move 5 pages forward, move to last page; another alternative: first, last, and a page selector dropdown)
4. add selectors that can restrict list to a specific number of days and number of results, like in http://crashreport.libreoffice.org/stats/version/5.2.0.4
5. add some kind of version selector, for example a dropdown or a tree view (example: https://www.jstree.com/ )

Tasks that need it:

• deleting uploaded crash reports after n days
• crash count generation
• potentially removing old crash counts
• getting MS system library symbols

This should enable us to see if we can add the corresponding symbol files in the future. Examples are the windows system libraries.

SEH makes the current signature code more or less useless. We should improve that and switch to a system where we blacklist some frames that are known to contain only SEH parts.