[Libreoffice-bugs] [Bug 140960] LibreOffice is crashing on exit and in daily use

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=140960

Michael Weghorn <m.weghorn at posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7.1.2.2 release             |6.2.5.2 release
             Status|NEW                         |NEEDINFO

--- Comment #11 from Michael Weghorn <m.weghorn at posteo.de> ---
(In reply to Mack Wang from comment #9)
>   I confirm that the bug is appearing in release 7.1.2.2. I also confirm
> that the bug is NOT happening if I open an empty document, wait a while, and
> close it.

Thanks for further testing.
The "Version" field is for the *earliest* affected version, so I'm setting it
back to the previous value.

Please set bugs back to UNCONFIRMED if you add the requested information. NEW
is the status that is set if somebody else could confirm/reproduce the bug.

>   Now a NEW bug is appearing and is causing data loss. In the previous bug,
> I reported that the KDE kept informing that soffice.bin is crashing even it
> is not. I also observed that sometimes, on next startup, a dialog appears
> asking me whether to recover the document or not, indicating that
> LibreOffice DID crash on exit. So, I modified the title of the bug to
> "LibreOffice is crashing on exit and in daily use". 
>   However, today I observed that soffice.bin IS CRASHING DURING USE. This
> happens when I am editing a .docx, and opened a .pptx for my reference.
> soffice.bin suddenly exited, and KCrashHandler did not notice that event!
> This is actually causing me data loss.
>   As a supplementary info, the bug appeared not on exit, but suddenly. Also
> KCrashHandler was not incited, so there is even no backtrace log. If you
> know how to generate a backtrace log in this circumstance, or if I need to
> use gdb or some stuff to debug soffice.bin, please email me.

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
has information on how to generate a backtrace.


Can you find exact steps to reliably reproduce this on your end?
If so, I suggest you start creating a fresh sample document with which this is
also reproducible that you can share, so somebody can try to reproduce and
analyze the issue with that one.

What I usually do in such cases is that I start with the original document,
then:

1) delete some content
2) try whether the issue is still reproducible
  * if yes: continue at step 1 (delete some more content)
  * if no: put the content back, try to delete some other content

This way, you can first minimize the existing document. Once you know what part
is the problematic one, you can try to create a fresh, non-confidential
document that has the same characteristic as the original one and also triggers
the crash. You could then share that non-confidential document.

I know this will take some time, but it is hard to fix bugs that are not
reproducible and whose backtrace doesn't show the problem at once. In case you
want to try this and/or have any questions, you can also ask them on IRC or the
QA mailing list, s. https://wiki.documentfoundation.org/QA/GetInvolved#Contact
for details.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210503/cf1c5863/attachment-0001.htm>