Created attachment 47704 [details] This file was migrated from Word 2000 and edited with OpenOffice 3.3.0. It is not possible to open with LibreOffice (system hangs). At our company we are migrating from MS Office 2000 to LibreOffice (3.3.2 and OpenOffice 3.2.0). The following files were migrated from Word 2000. After a while working with those they crash on opening. Our employees like working with tables and tables in tables and inserting pictures into those tables. This might cause the trouble. The first file attached does not open, the second hangs when you scroll and click into the second table from the bottom. A short note about possible solutions and the time frame would help me. It's really important to keep the migration project alive. Thanks for your work.
Created attachment 47705 [details] second file: LO hangs when srolling / clicking into a table Scroll to the second table from bottom called "Kondenswassertest" and click into it. => LO hangs.
Same behaviour with LibreOffice 3.4.0.
[Reproducible] with reporter'e "S_532 Konkurrenzanalyse 2K. PU-Grundierungen (Grundierfüller).odt" and "LibreOffice 3.4.0 – WIN7 Home Premium (64bit) English UI [OOO340m1 (Build:12)]". Both documents open fine when I dobleclick in WIN explorer, in document "S_532 ..." I see the problem that LibO will stop responding when I scroll down (using scroll slider) and reach page 5. OOo 3.1.1 also stops responding for several seconds reaching the same position, but after a short time problem disappears and from now on the document can be used without problems. Some tests with switching off auto spell check or auto correct did not solve the problem. We might have 2 problems: 1. incorrect conversion .doc -> .odt 2. Crash problem @Thomas Thym Can you please contribute some more information how those documents have been created? Can you please also attach the source .doc documents?
BTW, Thomas Thym: Can you confirm "Bug 37206 - Recovery window shows error report text"?
Thanks for your quick response. I tried to reproduce the error with the .doc files he though he was using, but without success. (Once you are looking forward to a crash and nothing is happening.) I will have a look into that tomorrow. Thanks for your help.
I could not reproduce the crash but I saw serious slowdown of application.
Not reproducible under Linux - even under valgrind; though I got this: ==16687== Error: File /data/opt/libreoffice/libreoffice-3-4/clone/libs-gui/unotools/source/config/configitem.cxx, Line 584: XHierarchicalNameAccess: Other/IsSquaredPageModeOther/ApplyCharUnit /org.openoffice.Office.Writer/Layout/Other/IsSquaredPageModeOther/ApplyCharUnit Backtrace: [0] /data/opt/TTInstall/program/../basis-link/program/libutlli.so: _ZN3utl10ConfigItem13GetPropertiesERKN3com3sun4star3uno8SequenceIN3rtl8OUStringEEE+0x517 Backtrace: [1] /data/opt/TTInstall/program/../basis-link/program/libswli.so: ???+0x6372f8 Backtrace: [2] /data/opt/TTInstall/program/../basis-link/program/libswli.so: ???+0x6379be but its clearly not fatal (perhaps I should re-compile utl without debug though).
Hi all, today we tried again to reproduce the bug, creating a crashing document. Again with no success. Is it useful if I attach the source files? They were heavily modified. Is there anything else we could do to help you? Cheers and thanks, Thomas
I just opened the document on my openSUSE laptop (LibreOffice 3.3.1 OOO330m19) with rather the same behavior. After a while very high cpu usage I could see the text in the first 5 columns as well. Clicking into the document restarted the high cpu usage and the text in the first 5 columns disappeared again.
I believe currently we should check the reproducible high CPU load here. @Thomas Thym: Currently this only has low priority because we have no information that lots of users might be affected. Here we urgently need information concerning your OS. Currently it looks like "WIN only"? I recommend to file a second report concerning a possible import problem (causing damaged documents). For that we need a source.doc, result.odt (showing the problems reported here) and a good description concerning the import process. So someone can check whether the import process creates damaged documents. I recommend to read hints on <http://wiki.documentfoundation.org/BugReport>, those hints might help you to create an optimum report with minimum costs. @Andras Timar: With what OS did you observe the slowdown? Please feel free to leave CC after having left information
OS -> ALL due to Comment 9 @Cédric: Please feel free to reassign if it's not your area!
(In reply to comment #10) > @Andras Timar: > With what OS did you observe the slowdown? Linux 32-bit and Windows.
I just tested the attached document with LO 3.3.3 on Ubuntu natty 64-bit. The first ("not possible to open") seems to work fine, no problems or even slowdown as far as I can tell. The second one though, caused 100% CPU when scrolling below the color-filled cells. Hope this helps! Best regards, Julian
I still see the scroll problem with and with "LibreOffice 3.5.2.2 German UI/Locale [Build-ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f] on German WIN7 Home Premium (64bit) Currently I see not many users and / or documents affected, so I remove this one from MAB 3.4. If you find that this affects a bigger number of documents please feel free to add to “Bug 37361 LibreOffice 3.5 most annoying bugs”
Opps, wanted to say "with S_532 Konkurrenzanalyse 2K. PU-Grundierungen (Grundierfüller)" and 3.5.2
On pc Debian x86-64 with master sources updated today, here what I got: File S528 PolyAmol: - opening OK - scroll OK File S532...: - opening OK - scroll KO from page 3 infinite loop with this: warn:legacy.osl:29699:1:/home/julien/compile-libreoffice/libo/sw/source/core/layout/tabfrm.cxx:2606: debug assertion: <SwTabFrm::MakeAll()> - format of table lowers suppressed by fix i44910
On pc Debian x86-64 with master sources updated yesterday, I reproduced the behaviour of my last comment, only the number line changed. warn:legacy.osl:7382:1:sw/source/core/layout/tabfrm.cxx:2633: debug assertion: <SwTabFrm::MakeAll()> - format of table lowers suppressed by fix i44910 Since no one is assigned, I put it at NEW.
Can still confirm on Win 8.1, LO 4.2.4.2.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Confirmed slowdowns. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: fcc2415ade6ae93710bbbda9f7e163045e323105 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-10-21_16:55:13 Locale: fi-FI (fi_FI)
Migrating Whiteboard tags to Keywords: (perf)
No repro with: Version: 5.4.0.0.alpha0+ Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-18_06:57:59 Locale: nl-NL (nl_NL); Calc: CL
(In reply to Julian Rüger from comment #13) > The second one though, caused 100% CPU when scrolling below the color-filled > cells. Ok now I do not see the CPU rise for this, let's close. Version: 5.4.0.0.alpha0+ Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-12-18_07:01:05 Locale: fi-FI (fi_FI); Calc: group