Bug 134997

Summary: Trying to save a Base file crashes LibreOffice
Product: LibreOffice Reporter: Dr. Martinus <linux>
Component: BaseAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: xiscofauli
Priority: medium    
Version: 6.3.6.2 release   
Hardware: All   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Dr. Martinus 2020-07-20 20:51:39 UTC
Description:
I had a few (~5) documents open, the last action I took was saving a writer document as pdf. Shortly before that, a few minor changes had been made to a report in the base file, which I saved right away. However, in the Base window it still showed the "unsaved" symbol, as usual. 
Then I left and returned after 2 hours and found that LibreOffice was hanging, the windows weren't restored. I waited several minutes, then tried to close any of the windows, and got each time the message: LibreOffice does not reply. So I ended it. After restart (after all files had been recovered), I closed the files which seemed fine to me. However, saving the Base module which still showed the unsaved state caused LibreOffice to crash and immediately to reopen with the recovery window. 
I still can open reports and databases within the database.
I tried saving the database under a different name. One of these attempts resulted in a 0 byte document, the other in a 1.9 kB file. 
Finally I managed to recover without grace by hitting the "close window" button and then on the file save dialog hitting "don't save". After that, it behaved normally again.


Steps to Reproduce:
1. Sorry, I can't reproduce that. See my description of the process.
2.
3.

Actual Results:
See the description

Expected Results:
See the description


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: OfficeDatabaseDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Version: 6.3.6.2
Build-ID: 6.3.6-2
CPU-Threads: 12; BS: Linux 5.6; UI-Render: Standard; VCL: kde5; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
Comment 1 Alex Thurgood 2020-07-21 10:25:10 UTC
@DrMartinus: unfortunately, if you lose the connection to the database context, for whatever reason, then there is a distinct likelihood that you will lose any data (including any changes) that may have been "in memory" at the time. This can lead to file corruption. 

Exclusive mutex handling and their respective release spring to mind with the scenario you describe...
Comment 2 Alex Thurgood 2020-07-21 10:25:57 UTC
Give that you don't appear to be able to reproduce it, this bug report will likely never get confirmed...
Comment 3 Xisco Faulí 2020-07-21 15:08:59 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 4 QA Administrators 2021-01-18 04:08:50 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-02-18 04:35:47 UTC
Dear Dr. Martinus,

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