Bug 154153 - [WRITER] [EDITING] copy-paste content with many tables into new file makes Writer crash (autorecovery maybe involved)
Summary: [WRITER] [EDITING] copy-paste content with many tables into new file makes Wr...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoSave-AutoRecovery-Backup
  Show dependency treegraph
 
Reported: 2023-03-12 22:23 UTC by loic_dupont
Modified: 2023-10-27 03:13 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
The "debug report" from BetterBird, that you can copy-past to reproduce the bug (39.52 KB, application/vnd.oasis.opendocument.text)
2023-03-12 22:25 UTC, loic_dupont
Details
screenshot of autosave recovery and file resulting. It's autosaving correctly, but crashing anyway. (370.12 KB, image/png)
2023-03-13 10:36 UTC, loic_dupont
Details

Note You need to log in before you can comment on or make changes to this bug.
Description loic_dupont 2023-03-12 22:23:18 UTC
Description:
BetterBird (ThunderBird fork) generate debug report, and allow to copy-paste it. When I copy paste it in a new file AND SAVE IT it's OK. 
But when I copy paste it and WAIT a while, it crash, and doesn't have managed auto-save. ...I think there is a problem with autosave with a file of this complexity. 
After crash, reopening Writer shows me that "there is a document to restore", but restored doc is blank.

Steps to Reproduce:
1. Create a new Writer file, and change "View" to "Web" (not "page") for easier view. 
2. Open the attached file.
3. Copy paste what is inside the attachement in your new created file. 
4. Wait for autosave... It should crash.

Actual Results:
Something make crash Writer (I think it's the autosave)

Expected Results:
Well, Writer shouldn't crash! :-/


Reproducible: Always


User Profile Reset: No

Additional Info:
I changed the "time before autosave"... And I crashed sooner. I strongly believe it's autosave that cause this, but I don't have proof. 
On the other hand, if you save it, it's OK. And if you save it and had "small changes", it's still ok. 
To reproduce the bug, you should copy-past the full document, and wait. 

For BetterBird users, to create a report on your own, use the BetterBird report menu in : "BetterBird > Help > More debug info > (it opens the debug page) > copy the content to clipboard". 

About Libre office : 
Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 24; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL
Comment 1 loic_dupont 2023-03-12 22:25:22 UTC
Created attachment 185918 [details]
The "debug report" from BetterBird, that you can copy-past to reproduce the bug

The file is redacted, but contains all tables generated by BetterBird debug page and "copy to clipboard" button.
Comment 2 loic_dupont 2023-03-12 22:26:00 UTC
There is no crash report generated.
Comment 3 Stéphane Guillou (stragu) 2023-03-13 09:14:02 UTC
Thanks for the report, Loic.

I tested with version 7.4.6.2 on Linux and could not reproduce the crash. I used Save AutoRecovery information every 1 minute".

There are no further bugfix version planned for LibreOffice 7.3
Could you please try to reproduce the crash with a version that's currently supported? 7.4 or 7.5.
Please let us know if it still happens.

Thank you!
Comment 4 Sophie Sipasseuth 2023-03-13 10:27:59 UTC
Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded

I tried to reproduce the crash with version 7.5.
And it doesn't crash, but the autosave doesn't work!
I have checked the autosave option and put it in 1 minute.
There is nothing happened again.
Comment 5 loic_dupont 2023-03-13 10:34:25 UTC
# Update done!
The good news is I updated to 
Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 24; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded
I don't know why I regressed to an old version, but it's up-to-date again. 
=> I changed the earliest affected version. 

# But it didn't solve it.
The not-so-good-news is that I still reproduce the bug. 
BUT there is a catch ! this time, the modification are saved via autosave BEFORE crash. ...But it is still crashing. 
=> I made a screenshot of the recovered files to show that it saved the modification, but still crashed. 
=> changed status to unconfirmed.

# What did I do : 
1. Closing all opened Libre office file. 
2. Updated to 7.5.1.2
3. Opened the attached file.
4. Copied and paste what is inside the attachment in your new created file. 
5. Made a small modification to test autosave (i did NOT save the new document)
6. Waited for autosave... It crashed.
7. re-opened Writer
8. made screenshot for recovery
9. opened recovered files
10. discovered an autosaved file WITH the modification saved. Screenshot + info added and merged with recovery screenshot.
11. finally updated this bug file.

Hope it helps. 

# Context, and what can I do ?
I have a (quite?) stable machine, it's only LibreOffice that is crashing so often. 
It's a (quite again) new machine less than 2 years old, top of the line (PC master race!), with big muscles, actually, even with dozens of firefox tabs open and different apps running, processor is loaded only from  2% to 6%, and RAM is loaded 9.6 / 31 Go. 
I would (but don't know how to) help with a dump or a "debug mode" for LibreOffice if existing and needed. 

PS : I'll upload the screenshot after submitting this comment.
Comment 6 loic_dupont 2023-03-13 10:36:16 UTC
Created attachment 185924 [details]
screenshot of autosave recovery and file resulting. It's autosaving correctly, but crashing anyway.

see comment 5 to understand context. (TLDR : I updated to 7.5, now it's correctly autosaving, but still crashing my Writer, without crash report)
Comment 7 Sophie Sipasseuth 2023-03-13 13:13:21 UTC
Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded

Indeed, the first time I didn't do any changes to the document.
Now when I make a change to the document, after 1 minute, I can observe a loading icon appear on my screen for just one moment.
But, the document isn't saved.
And when I want to close the document, a message appears to make me understand if I don't save the document before, it will be lost.
So, I confirmed this bug.
Comment 8 BogdanB 2023-03-13 15:25:00 UTC
No crash on
Version: 7.5.1.1 (X86_64) / LibreOffice Community
Build ID: bd819218336a5be54a11b986ea4dd2db2efb120e
CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: en-US (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 9 Sophie Sipasseuth 2023-03-28 08:30:31 UTC
No matter if the document was saved or not before I make a modification to this one, Libre Office makes an autosave. But it is still necessary to save the document manually to not lost the modification before closing it. So I don't see any crashes with this version of Libre Office. But I don't understand why it is still necessary to save the document manually after an autosaved. 

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4daeb21a5f533144fd6b3bc397a98f37e5b1dd4c
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded
Comment 10 Stéphane Guillou (stragu) 2023-03-29 15:59:51 UTC
(In reply to Sophie Sipasseuth from comment #9)
> No matter if the document was saved or not before I make a modification to
> this one, Libre Office makes an autosave. But it is still necessary to save
> the document manually to not lost the modification before closing it. So I
> don't see any crashes with this version of Libre Office. But I don't
> understand why it is still necessary to save the document manually after an
> autosaved. 

Sophie and Loic, the autorecovery function is about automatically saving recovery information, as opposed to saving the document itself. It's a safety net, not an autosave at every change like we are getting accustomed to in e.g. cloud apps.

See the help page: https://help.libreoffice.org/7.5/en-US/text/shared/guide/doc_autosave.html
See that autosave was made unavailable back in LO 5.0: https://bugs.documentfoundation.org/show_bug.cgi?id=65509#c33

Let's focus on the crash here.
Loic, I could not reproduce the crash following the steps in comment 5.

I used a 1-minute autorecovery setting with:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 002f941ec20e594e9702c39fab9cf9f4cc392dab
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

If you are able to, could you try getting a windbg backtrace? Instructions are here: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Another thing to test is to see if it still crashes in safe mode: Help > Restart in safe mode.
Comment 11 QA Administrators 2023-09-26 03:14:32 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2023-10-27 03:13:44 UTC
Dear loic_dupont,

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