Task #3518
closed
Windows crashreports at crash.libreoffice.org have useless backtraces (breakpad update needed?)
70%
Description
I have recently analyzed recent reports at crashreport.libreoffice.org and it appears that the vast majority of recent Windows crashreports have useless backtraces, with many frames not resolved to function names or the backtraces having only few frames.
I'm not sure what's caused this, but random observations:
- Linux backtraces seem to work fine (https://crashreport.libreoffice.org/stats/crash_details/c249c48f-5919-425b-bd9d-bb5dc1a34680)
- Backtraces involving Skia (built with Clang) are fine for frames in Skia (https://crashreport.libreoffice.org/stats/crash_details/e1b81d2a-1358-486f-9d81-4f8303e5be0c)
- 32bit (x86) backtraces appear to be fine (https://crashreport.libreoffice.org/stats/crash_details/473f460a-a782-413b-96e1-3e00bd7bfed0), although not all of them (https://crashreport.libreoffice.org/stats/crash_details/b2c17b07-8b32-469b-aedd-61bf13e095fc)
- Reports that are 1 year old appear to be broken (https://crashreport.libreoffice.org/stats/crash_details/6184857d-80dc-4964-bfb5-7e0cd84f40ad)
- Reports that are 2 years old appear to be fine (https://crashreport.libreoffice.org/stats/crash_details/7ad871cb-e187-44eb-bb5a-05a9cc792b0d)
Note that those URLs are just examples, I used psql queries to gather 10k+ crashreports from the most recent LO release from this year and practically all of them are useless.
Our snapshot of the breakpad library is from 2015, so one possible explanation is that this old snapshot cannot properly handle backtraces from recent MSVC 64bit builds. I have a Gerrit change with a recent breakpad snapshot ready, but I expect that the server side on crashreport.libreoffice.org needs to be updated first.
Can somebody please look into this?