Re: Some comments regardig https://github.com/audacity/audacity/pull/836
Joost Andrae <[email protected]> Wed, 12 May 2021 09:37:15 +0200
| Newsgroups | gmane.comp.audio.audacity.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi James, regarding the DB backend logics I cannot say anything as it doesn't exsist anymore and the Apache OpenOffice team decided to deactivate the feature. AFAIK LibreOffice still uses some sort of crash reporting functionality. I'm not sure if they use breakpad. https://crashreport.libreoffice.org/stats/ https://github.com/mmohrhard/crash I must warn about the overhead on server side, because each released build needs to be archived with debug information (that's very expensive !) because you need the debug information to attach library names to the stack IDs. For OpenOffice.org it ment to store massive GB locally for each build within the local server environment of the StarOffice/OpenOffice.org development team at Sun Microsystems in Hamburg. Kind regards, Joost Am 11.05.2021 um 17:18 schrieb James Crook: > Thanks Joost! > > That sounds good, and not a contentious use of TCP/IP at all, > especially as explicit opt-in on each and every crash. > > Can you say more about the processing at the receiving end?? > Lots of time and work on tools there?? My expectation is that > some crashes will have very repeatable stack traces, often due > to a recent change in our code, but some won't, and I wonder > particularly how you dealt with those? > > Is it one of those cases where 90% of the benefit comes easily, once > set up, and that alone makes it worthwhile doing? > > --James. >