Bug 98022 - LibreOffice freezes while saving large file
Summary: LibreOffice freezes while saving large file
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Performance
  Show dependency treegraph
 
Reported: 2016-02-20 14:26 UTC by Bart Hengeveld
Modified: 2023-04-12 16:56 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Large document that freezes LO on saving (9.22 MB, application/vnd.oasis.opendocument.text)
2016-04-08 12:07 UTC, Bart Hengeveld
Details
WinDbg backtrace (8.92 KB, text/plain)
2016-05-09 14:57 UTC, Aron Budea
Details
file saved with LO 6112-64 win10-64 (9.60 MB, application/vnd.oasis.opendocument.text)
2018-09-17 11:22 UTC, paulystefan
Details
console logs (31.48 KB, text/plain)
2020-01-22 15:41 UTC, Julien Nabet
Details
console logs (Linux) (4.83 KB, text/plain)
2020-01-22 19:16 UTC, Julien Nabet
Details
perf flamegraph (159.52 KB, application/x-bzip)
2020-01-22 19:31 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Hengeveld 2016-02-20 14:26:49 UTC
When trying to save a 8.6085KB writer file LibreOffice freezes.
OS: Windows 10 pro, 10.0.10586 build  10586.
LibreOffice 5.1.0.3
Processdump added
Comment 1 Bart Hengeveld 2016-02-20 14:27:40 UTC
Processdump too large for uploading, but available
Comment 2 Buovjaga 2016-02-21 15:50:19 UTC
Does it help, if you disable Tools - Options - LibO - View - Use OpenGL for all rendering and restart LibO?
Comment 3 Bart Hengeveld 2016-02-22 06:25:29 UTC
I already tried that, makes no difference.
Earlier versions 4.* handled the file without problems. Also OpenOffice 4.1.2 handles this file OK.
Comment 4 Buovjaga 2016-02-22 10:11:45 UTC
Could you upload the processdump to some online file host?
Comment 5 Bart Hengeveld 2016-02-22 13:13:29 UTC
(In reply to Beluga from comment #4)
> Could you upload the processdump to some online file host?

Can not change ownership, file refused by hosters. Please provide email address for we transfer alert.
Comment 6 Buovjaga 2016-02-22 13:40:05 UTC
(In reply to Bart Hengeveld from comment #5)
> (In reply to Beluga from comment #4)
> > Could you upload the processdump to some online file host?
> 
> Can not change ownership, file refused by hosters. Please provide email
> address for we transfer alert.

Can't you use something simple like http://tinyupload.com/
Or is it over 50MB?
Comment 7 Bart Hengeveld 2016-02-23 08:48:27 UTC
It is 533MB. Tried several of these. Now uploading to dropbox. made a user "iedereen" giving full control. Will provide link when ready.
Comment 8 Bart Hengeveld 2016-02-23 09:02:44 UTC
https://www.dropbox.com/s/6ym1t0t1vqwyig3/soffice.DMP?dl=0

this is where you should be able to dollect the process dump.
Comment 9 Bart Hengeveld 2016-03-04 08:44:01 UTC
Is there any solution found for this misbehaviour?
Could you download the process dump?
Comment 10 Buovjaga 2016-03-04 09:51:37 UTC
(In reply to Bart Hengeveld from comment #9)
> Is there any solution found for this misbehaviour?
> Could you download the process dump?

I'm not a developer.
Comment 11 Bart Hengeveld 2016-03-11 10:19:13 UTC
The latest 5.1.1.3 solves the freezing of the saving operation.

Can you perhaps alsolook into the way that LibreOffice is installing. As it is now it first cycles through the early parts of the installation process and then asks for the admin password and then starts the process anew. Could this be changed so that the admin password is asked for immediately. This would speed up the installation process.
Comment 12 Buovjaga 2016-03-11 13:36:08 UTC
Thanks for testing! Setting to WFM.
Comment 13 Bart Hengeveld 2016-03-13 20:36:05 UTC
Sorry, but same issue returned: freezes on saving large file.
Comment 14 Buovjaga 2016-03-14 06:51:36 UTC
Please try this trick as well: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile
Comment 15 Buovjaga 2016-03-14 13:56:23 UTC
You could try

!analyze -hang

to replace !analyze -v in these instructions: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

You can read about it in the Windbg help.

I also read this page: https://developer.mozilla.org/en-US/docs/Mozilla/How_to_get_a_stacktrace_with_WinDbg

It has these steps after breaking out (Debug - Break):
~* kp
!analyze -v -f

!analyze -f means: Generates the !analyze exception output. Use this parameter to see an exception analysis even when the debugger does not detect an exception.
Comment 16 Buovjaga 2016-03-14 14:08:22 UTC
Or better:
!analyze -v -hang
Comment 17 Bart Hengeveld 2016-04-08 07:51:27 UTC
Version 5.1.2.2 doed not solve the problem. Libreoffice stille freezes when trying to solve the document.
Would it help if I sent you the document in question?
Comment 18 Buovjaga 2016-04-08 08:42:07 UTC
(In reply to Bart Hengeveld from comment #17)
> Version 5.1.2.2 doed not solve the problem. Libreoffice stille freezes when
> trying to solve the document.
> Would it help if I sent you the document in question?

Does it contain confidential information? If not, you could attach it to the bug report.

If it is confidential, I guess I could make an exception and try to analyze it privately (after you email it to me). But if I can't get a useful trace, it won't help.
Comment 19 Bart Hengeveld 2016-04-08 09:34:05 UTC
I tested this also in my linux machines. Both saves the document without problems. It concerns older (one even very old) machines with limited memory and old processor. 
One machine with AMD Sempron 2500+ running Lubuntu 14.04.4 LTS, with 1285 mb
The other machine running Bodhi linux 2.4.0, pentium III, 768 mb.
Comment 20 Buovjaga 2016-04-08 09:57:25 UTC
(In reply to Bart Hengeveld from comment #19)
> I tested this also in my linux machines. Both saves the document without
> problems. It concerns older (one even very old) machines with limited memory
> and old processor. 
> One machine with AMD Sempron 2500+ running Lubuntu 14.04.4 LTS, with 1285 mb
> The other machine running Bodhi linux 2.4.0, pentium III, 768 mb.

Aha. If those two machines work ok, what oldie do you have that freezes? I don't know, if something arising from limited memory can be considered a bug..
Comment 21 Bart Hengeveld 2016-04-08 11:53:46 UTC
The saving freezes LibreOffice on my Windows 10 pro (Versie 10.0.10586 Build 10586) machine:
Dell Inspiron 545, Processor	Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz, 2331 MHz, 4 core('s), 4 logische processor(s), memory 4GB.
Comment 22 Buovjaga 2016-04-08 12:01:33 UTC
Ah, so it was the other way around.

Is there a reason you are not attaching the file?
Comment 23 Bart Hengeveld 2016-04-08 12:07:30 UTC
Created attachment 124185 [details]
Large document that freezes LO on saving

Please find attached the document that freezes LO when I try to save it on my win 10 PC. Note the Open Office handles this file without any problems anf LO handles the file Ok when run in a linux environment.
Comment 24 Buovjaga 2016-04-12 10:53:28 UTC
(In reply to Bart Hengeveld from comment #23)
> Created attachment 124185 [details]
> Large document that freezes LO on saving
> 
> Please find attached the document that freezes LO when I try to save it on
> my win 10 PC. Note the Open Office handles this file without any problems
> anf LO handles the file Ok when run in a linux environment.

Does not freeze for me.

Win 7 Pro 64-bit, Version: 5.1.2.2 (x64)
Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)
Comment 25 Bart Hengeveld 2016-04-12 11:07:57 UTC
I am using Windows 10 pro, build 10586, and under this operating system I encounter the described freezing. Open Office 4.1.2 handles the file OK.
So I do not know about how how the file would be handled under Windows 7 as I do not have that.
Comment 26 Aron Budea 2016-05-09 14:57:30 UTC
Created attachment 124937 [details]
WinDbg backtrace

Can reproduce with Windows 7, 64-bit. During save the status indicator fills to about halfway, then stops, and nothing happens.

Version: 5.1.2.2 (32-bit)
Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: hu-HU (hu_HU)

Does not occur with 32-bit debug build on master.
Comment 27 QA Administrators 2017-05-22 13:40:42 UTC Comment hidden (obsolete)
Comment 28 paulystefan 2018-09-17 11:22:20 UTC
Created attachment 144937 [details]
file saved with LO 6112-64 win10-64

i saved file with no problem in LO 6112-x64 in win10-x64. 

Size increases about 5%.

no frozen program in my system
Comment 29 QA Administrators 2019-09-18 02:53:49 UTC Comment hidden (obsolete)
Comment 30 Julien Nabet 2020-01-22 15:41:03 UTC
Created attachment 157331 [details]
console logs

On Win10 with LO master sources updated today, I don't reproduce the freeze but it takes some time to save.
Comment 31 Julien Nabet 2020-01-22 15:44:42 UTC
I also tested with LO 6.3.4 (still on Win10), since it's a a not debug build, it takes some time too but the file can be saved.
However, in both case, at about 1/5 of progress bar during saving, it seems to freeze but I just waited a bit.
I'll try to retrieve a Flamegraph on Linux.
Comment 32 Julien Nabet 2020-01-22 19:16:08 UTC
Created attachment 157338 [details]
console logs (Linux)

Here are console logs from pc Debian x86-64 with master sources updated yesterday.
Comment 33 Julien Nabet 2020-01-22 19:31:33 UTC
Created attachment 157339 [details]
perf flamegraph

Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today.
Comment 34 Telesto 2020-06-12 12:11:51 UTC
1. Attachment 124185 [details] doesn't freeze anymore.. still not fast.. but copy/paste to a new document and the issue is gone

The bug has changed too, I think.. Original related to OpenTTFont handling.. Now it turned into a graphics issue


MsgWaitForMultipleObjects
osl_waitCondition
salhelper::ConditionWaiter::ConditionWaiter
utl::UCBContentHelper::getDefaultCommandEnvironment
utl::UCBContentHelper::getDefaultCommandEnvironment
utl::UCBContentHelper::getDefaultCommandEnvironment
utl::UcbStreamHelper::CreateStream
utl::UcbStreamHelper::CreateStream
vcl::graphic::loadFromURL
sfx2::LinkManager::GetGraphicFromAny
SwSectionFormat::supportsFullDrawingLayerFillAttributeSet
SwGrfNode::IsFrameInPaint
SwGrfNode::SwapIn
SwGrfNode::MakeCopy
Comment 35 Julien Nabet 2020-06-13 08:00:49 UTC
No freeze here too, I don't know what should be done here for this tracker.
=> uncc myself.
Comment 36 QA Administrators 2022-06-14 03:28:25 UTC
Dear Bart Hengeveld,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug