Description: FACTS: I'm using LO 7.0.3.1 writer on Win7 with approx 280 pages in a single ODT document. My ODT document contains written text, tables, and 250 or so resized medium resolution jpg images within Frames. My ODT data file is formatted in book-like fashion to perhaps be published. When I tried to add one more jpg image LO crashes (hangs). I can't access, update, or save my updated ODT file. LO doesn't crash when I open smaller LO data files. My LO ODT data file that crashes is approx 75MB. I reinstalled an earlier LO version and the problem still occurs. Interestingly, when I open a much smaller document containing images LO doesn't crash. For some strange reason it seems LO can't properly handle the large size and complexity of my .odt file. A few of my ODT images are 'compressed' using LO. Others are compressed using Photoshop. I don't want to abandon LO because it is a great software application that I have routinely used for years. QUESTIONS: (1) Is there a problem with LO7 (and earlier versions) with large writer ODT files containing many large images, captions, tablers, etc? (2) Any solutions for the hangup problem? (3) How do I recover my ODT file? NOTE: I can't disclose content of my large document because it's confidential. Actual Results: See above Description of crash description. Expected Results: It crashes/hangs. can't do anything with LO once it crashes. The bottom line shows "Loading document". Expected results: document should have been loaded and accessible for editing. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
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. (Note that the attachment will be public, remove any sensitive information before attaching it. See the QA FAQ Wiki for further detail.)
1. I can't open my ODT file. When I try to open it, LO Writer simply hangs. 2. I can't send you my ODT data file because it is confidential preventing me from disclosing its content.
Here is LibreOffice's info on the crash as displayed on my computer: Problem signature: Problem Event Name: AppHangB1 Application Name: soffice.bin Application Version: 7.1.0.1 Application Timestamp: 5fe0aea6 Hang Signature: 41d1 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Hang Signature 1: 41d14a07f412abb51e7c59723139db62 Additional Hang Signature 2: 2807 Additional Hang Signature 3: 28072662d24236c2074800053da32aef Additional Hang Signature 4: 41d1 Additional Hang Signature 5: 41d14a07f412abb51e7c59723139db62 Additional Hang Signature 6: 2807 Additional Hang Signature 7: 28072662d24236c2074800053da32aef Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
I can't disclose content of my large document because it's confidential.
[Automated Action] NeedInfo-To-Unconfirmed
You could try opening the file in safe-mode with the older version (or newer) help -> safe mode Or copy paste the content into new document.. this sometimes helps.. The last solution might be sending to specific person (release engineer) or attempting to anonymize the file, buts no help for images
You can upgrade to 7.0.4 + try https://wiki.documentfoundation.org/QA/FirstSteps For backtrace, you can try: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace For the rest, I'm not astonished considering the size of the document and knowing the leaks and perf pbs that LO may have. Hope you've already made backups of your file. I think perhaps you should also consider splitting the file.
(In reply to Telesto from comment #6) > You could try opening the file in safe-mode with the older version (or newer) > help -> safe mode > > Or copy paste the content into new document.. this sometimes helps.. > > > The last solution might be sending to specific person (release engineer) or > attempting to anonymize the file, buts no help for images I tried opening my ODT file in safe-mode, but LO froze again. I also tried an earlier and the latest LO version, but LO still freezes. Bottom line, I'm unable to open my last updated ODT file. Unless I can find a work-around I'm stuck with opening an earlier version of my ODT file. That means I've lost all updates because I can't even access them.
(In reply to Julien Nabet from comment #7) > You can upgrade to 7.0.4 + try > https://wiki.documentfoundation.org/QA/FirstSteps > > For backtrace, you can try: > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows: > _How_to_get_a_backtrace > > For the rest, I'm not astonished considering the size of the document and > knowing the leaks and perf pbs that LO may have. > > Hope you've already made backups of your file. I think perhaps you should > also consider splitting the file. Julien - I tried 7.0.4 and I got the same LO hangup/freeze. Yes, I've made backups of all prior ODT updates, except for my last update where I added more JPGs and text. These last additions are now all lost because I can't open the updated ODT file. Bummer! As for splitting the file I have a table of contents at the front end of the document and will likely have an INDEX at the end. Splitting a big file as you suggest defeats the ability to do auto updates to a TOC and INDEX. If a solution isn't found for the main issue I may have to go the route you suggest. Thanks for your suggestion. :) :(
I would back out the LibreOffice 7.1.0.1 that build has Windows clipboard issues of bug 139074 Also, as you are on Windows 7 Sp1, there is a good chance you will have GPU graphics issues with Skia rendering. I would suggest you roll back to 6.4.7.2 release, and disable both OpenGL and Skia rendering (your choice about the Hardware acceleration under CPU control, I tend to disable it as well). Then with default GDI based rendering enabled, see if your document will open cleanly. If that clears things, please post the GPU and driver details from your system (both the skia.log and from the Windows msinfo32.exe -> components -> display dialog).
Thank you for the suggestions. I will do and see if it solves my issue(s).
Here are more facts: 1. I tried opening my large ODT file with LO 6.4.7.2 on my Win7 cpu. Writer still crashes during the attempted ODT open process. 2. I should note sometimes when Writer crashes the screen momentarily blinks totally black several times. Sometimes it remains black until I kill the running LO app. 3. Next, I tried opening the large ODT file on my Windows10 computer. LO also crashes when trying to open the same large ODT file. So it doesn't look like the operating system is the cause. :) NOTE: I didn't disable OpenGL and Skia on either CPU system.
> Bottom line, I'm unable to open my last updated ODT file. Unless I can find > a work-around I'm stuck with opening an earlier version of my ODT file. > That means I've lost all updates because I can't even access them. With a program like 7zip, you can try to open the file as archive. Your text *should* still be there as xml and your pics in a seperate drawer.
I don't have 7zip, but I do have WINZIP. Will Winzip unzip the text and images?
(In reply to Hal from comment #15) > I don't have 7zip, but I do have WINZIP. Will Winzip unzip the text and > images? Yes Winzip will unzip your file. An ods/odt/odb... is in fact a zip file which contains a specific set of files. So you can rename your ods/odt/odb... file in zip and unzip it with Winzip. About 7zip, it's a free and opensource software see https://en.wikipedia.org/wiki/7-Zip or https://www.7-zip.org/. It can uncompress, zip, rar and other formats, bzip, arj, etc.
Installed 7-zip. Was able to retrieve images, but can't seem to display the more important lost text (supposedly converted to XML format) using LibreOffice. Guess I'll have to wait until LO figures out a solution for the LO crashes as I earlier reported. Thanks for your comments though including Julien's last comment. I appreciate it.
More data/info: Attempting to Insert a small jpg image (64KB) causes LibreOffice to crash. Any help by the 'pros' on the horizon? Until the LO bug is fixed I'm unable to proceed with my large-scale Writer project containing lots of formatted text, tables, images, captions, & indices.
(In reply to Hal from comment #17) > Installed 7-zip. Was able to retrieve images, but can't seem to display the > more important lost text (supposedly converted to XML format) using > LibreOffice. Text will be in the ODF zip archive in the file "content.xml"; it is sequentially built so newest text will be toward the bottom. The text "runs" will be mixed together with formatting & style notations and URI for the images, but with some judicious find and replace should get you back the text. If you need a good text editor to do this I'd suggest the notepad++ project [1], or alternatively the gvim project [2]. But vim syntax, while powerful for search and replacement, is a little daunting. If you don't want to invest the time, the GUI based notepad++ editor should work well. Good luck with recovery. =-ref-= [1] https://notepad-plus-plus.org/ [2] https://www.vim.org/
Thank you V Stuart Foote.
(In reply to Hal from comment #18) > More data/info: Attempting to Insert a small jpg image (64KB) causes > LibreOffice to crash. > > Any help by the 'pros' on the horizon? > > Until the LO bug is fixed I'm unable to proceed with my large-scale Writer > project containing lots of formatted text, tables, images, captions, & > indices. FRY - NEW INFO: Dragging a small jpg image into my very large .ODT file seems to work whereas trying to Insert it crashes LibreOffice.
FYI (not FRY) :)
FYI - the following link might be very relevant to solving my problem because (1) many, if not most, of my images are large file sizes, and, (2) my 'autorecovery' setting was enabled. See link: https://ask.libreoffice.org/en/question/227674/how-do-i-get-the-images-back-that-have-disappeared-from-my-writer-document/
Hello Hal, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Hal, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
It's been a long time and reporter had to do move on, so understandably not responding. But for this bug, only way I can think of was for him to send a file to a single member of LO QA team, like me or Xisco to test with different LO versions and to anonymize the document and attach it here. I remove "wantBacktrace" because not possible without the file. By description this may be meta bug 47148 but no point in relating if no file.
Dear Hal, 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