Bug 156692 - Crashing after update, no auto-save
Summary: Crashing after update, no auto-save
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.7.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: dataLoss
Depends on:
Blocks:
 
Reported: 2023-08-09 08:48 UTC by Kevin Neff
Modified: 2024-05-02 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Neff 2023-08-09 08:48:29 UTC
Description:
I just updated to 7.4 after being prompted by LibreOffice today, and it has now crashed on me twice, erase several hours of work both times.  Even though a recovery option is given, it does not recover the work I have done.

Steps to Reproduce:
1. I have no idea, I have just been working for an arbitrary amount of time, I go to switch between windows and it crashes.
2.
3.

Actual Results:
Terrible

Expected Results:
That an application doesn't crash with routine use


Reproducible: Always


User Profile Reset: No

Additional Info:
None.
Comment 1 Julien Nabet 2023-08-09 10:13:02 UTC
On which env are you? (Linux, macOS, Windows)
Could you upgrade to LO 7.5.5 + apply https://wiki.documentfoundation.org/QA/FirstSteps and give a new try?
Comment 2 Kevin Neff 2023-08-09 16:21:40 UTC
Windows.
Will download 7.5.5 and monitor use for issue recurrence.
Comment 3 Julien Nabet 2023-08-09 17:29:42 UTC
(In reply to Kevin Neff from comment #2)
> Windows.
Which Windows version?
Indeed, I saw some LO bugtrackers related to Windows 11.
Also, which processor: x86-32, x86-64, ARM ?

> Will download 7.5.5 and monitor use for issue recurrence.

Ok + don't forget https://wiki.documentfoundation.org/QA/FirstSteps in my previous comment.
Comment 4 Kevin Neff 2023-08-12 05:42:46 UTC
Still occurring after update, though less frequently.  Windows 10 Pro, 64-bit.
Not sure how to action suggestions in first step link and the only one that seems relevant right now is the user profile corruption.
Comment 5 Julien Nabet 2023-08-12 08:26:40 UTC
I(In reply to Kevin Neff from comment #4)
> Still occurring after update, though less frequently.  Windows 10 Pro,
> 64-bit.
> Not sure how to action suggestions in first step link and the only one that
> seems relevant right now is the user profile corruption.

It can be https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile but also https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_(_Skia_) or even https://wiki.documentfoundation.org/QA/FirstSteps#Fonts_issues if you installed some specific fonts.

Of course, it may be specific to your document, if it's the case, we need:
the document sanitized (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)
and above all, a step by step process to reproduce this but since you said at the initial comment you don't know what triggered this, it's gonna be hard.

Another thing you can try instead is to retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace) but it needs some work and patience.
Comment 6 Stéphane Guillou (stragu) 2023-10-03 14:20:18 UTC
Thanks Kevin.

- Which component were you using when it crashed? Writer, Calc, other, any?
- Could you please try updating again to the latest version (preferably 7.6.2.1)?
- If it still crashes, please paste here the full information copied from Help > About LibreOffice (as it tells us important things, like Skia-related information)
- Do you get a crash report dialog when it crashes? If so, please provide us with the URL to the crash report.
- See also the questions in comment 5. A backtrace would be ideal, but it does take some effort.

I'll mark as "needinfo" for now as we require more info to hope to resolve this.
Much appreciated!
Comment 7 QA Administrators 2024-04-01 03:12:13 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-05-02 03:15:33 UTC
Dear Kevin Neff,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp