Created attachment 144306 [details] a selfmade german-oldnorse dictionary from an internet source when i am working with large and complex documents, writer usually freezes. it happens every time i am working with some documents, so writer nearly became usless for me. this happens with virtually every little step, like deleting a letter. it just recently happened - in a different document - that i wanted to delete all "sections" of a document an froze again
Created attachment 144308 [details] libre office freezing after going to page 4/220 See the video I made with 6.1 freezing just when at page 4/220. Not changeing anything... Version: 6.1.1.0.0+ Build ID: 5a56b72413d5f555c854e36d3bd2fd50ec21644c CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-1, Time: 2018-08-15_02:45:13 Locale: ro-RO (ro_RO.UTF-8); Calc: group threaded
Confirmed with LibreOffice 6.1.1.0.0+ built at home under Ubuntu 18.04 x86-64. Set status to NEW. Best regards. JBF
Repro with Version: 6.2.0.0.alpha0+ Build ID: 414ef6cb187dd3bbcc917dbedf3c0c1cc8668f60 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-08-20_22:43:18 Locale: nl-NL (nl_NL); Calc: CL it's initially working better with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL However eventually it will hang (consuming all resources) after a minute or so No repro with as far I can tell (except with the spell checker enabled) Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
This should be bibisectable (with spell-checker disabled) assuming: * my comment 3 about 4.0.0.3 is right * and with Linux also affected
I tried 3 times to bisect this issue but the results weren't correct... If someone wants to try, I tried with bibisect-50max cleaning the user profile every time with rm -rf opt/user/. I followed these steps: 1. Load the document 2. Wait until the word count reaches ~250.000. 3. Scroll down with the page down key...
I bibisect with 5.4. Every instances went wrong!... With freezing... I have got an error, see here: javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx bogdan@bogdan-H110M-S2H:~/Libre Office bibisect/bibisect-linux-64-5.4$ ./instdir/program/soffice javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx bogdan@bogdan-H110M-S2H:~/Libre Office bibisect/bibisect-linux-64-5.4$ git bisect bad 867d029ef1568acc8e42c9974baee3d1ff85663a is the first bad commit commit 867d029ef1568acc8e42c9974baee3d1ff85663a Author: Jenkins Build User <tdf@pollux.tdf> Date: Tue Feb 7 14:21:17 2017 +0100 source 6b14e198d31f3189b2f574898dbe6bf6067643ba source 6b14e198d31f3189b2f574898dbe6bf6067643ba :040000 040000 6bcb642ac4736cc212bb191197d6129289d4d83c 2aa3809384d7d3cc1ea9d9f8da07c4dbc5308f44 M instdir
(In reply to BogdanB from comment #6) > I bibisect with 5.4. Every instances went wrong!... But that was known already :) Like Xisco said, the bibisecting should be attempted with bibisect-50max
(In reply to Buovjaga from comment #7) > (In reply to BogdanB from comment #6) > > I bibisect with 5.4. Every instances went wrong!... > > But that was known already :) Like Xisco said, the bibisecting should be > attempted with bibisect-50max Not totally convinced about the 50max repro (but surely no need to check 5.4). I could reproduce the issue with "oldest" in bibisect-50max. By scrolling up & down the document randomly.. (last page, first page etc) It's a nasty bug to bibisected, because it's harder to trigger the "layout loop" with older version.
Created attachment 144415 [details] GDB trace of freeze with master It got stuck upon opening with gdb. Killed process and this is the result. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: d30e76eb7854e9a4f170677719ad0ac3f92ef297 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on August 23rd 2018
Dear gambacherkalbenstein, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible with LO 6.3.3.0+ and current master, both built at home under Ubuntu 18.04 x86-64 Best regards. JBF
Hi Julien, Any chance we could have a perf chart here ?
Created attachment 154393 [details] perf flamegraph Here's a Flamegraph from master sources updated today (203865e128ddea66041bb1597333dfb04ec81186)
Michael: thought you might be interested in this one since Flamegraph shows that LO spends a lot of time in layout part (PrepareMake, MakeAll, etc).
Dear gambacherkalbenstein, 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
Still an issue in Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 817b8fe7001a83cb74910eb09b7c14a3b95b8a39 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: de-DE (hu_HU); UI: en-US Calc: threaded Document contains 2 tables that span all 220 pages.