<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - How shall we react if we encounter a crash report?" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126488#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - How shall we react if we encounter a crash report?" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126488">bug 126488</a> from <a class="email" href="mailto:adalbert.hanssen@gmx.de" title="Adalbert Hanßen <adalbert.hanssen@gmx.de>"> Adalbert Hanßen</a> <pre>(In reply to Dieter Praas from <a href="show_bug.cgi?id=126488#c12">comment #12</a>) > (In reply to raal from <a href="show_bug.cgi?id=126488#c3">comment #3</a>) ... > > Adalbert, normally you only have to copy ID and paste it into browser. If > there is no crash ID it could be a bug. As raal wrote, please give us some > steps to reproduce and also informations from Help => About LibreOffice. > > AFAIK there is no crash ID in a developer version (but I might be wrong) > > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' once the steps are provided. I just encountered another message that LO Writer crashed and wants to recover the documents on which I worked last. The crash message still looked the same as when I reported this bug. It did not tell me any crash ID. This happened with LO Writer Version: 6.4.0.0.alpha0+ Build ID: 0fb2927a8fe06e6c3255544b8e4c4c9c0f5a67d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-08-27_22:50:23 Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded I think it is especially important for the development version that it creates crash reports. Also the message which comes up after a crash report should give more information on the type of bug and it should ask some information in addition from the user, e.g. 1. How was the CPU usage and the memory usage at the moment, when the crash happened (I have a small indicator on by task bar which roughly tells me, if the CPU is at its limits or if memory is congested or if swapping takes place, so I have an idea if this could be the cause), 2. If LO just did not respond, 3. If the rest of the computer reacted to user input or if it was also tremendously slowed down, 4. How many documents were open (and are proposed to be reconstructed) when the crash happened? what is the file size of those files (in MB, also in estimated number of pages when printed - at least for the document which was under work when the crash happened) 5. If the user remembers what he did last before the crash happened. 6. Any other reasonable question the programmers conceive. Since the message of a past crash event happens after it by some other program than just the crashed LO, it certainly could collect and communicate such reasonable information to the programmers/debuggers.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>