Created attachment 119917 [details] the generated text I deleted an image with the option record changes on. The document became unresponsive. It turned out that Writer had inserted a lot of identical images. See the attachment. This bug is, I think, linked to record changes. The logic behind is not correct for images and memos.
The bug triggered if the changes are recorded and an image is replaced, I think.
Hello Aron, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 120093 [details] With text without text but with correct xml the last </text:tracked-changes> was added to make it a correct xml file. It was not in the original source file.
The attachment is made by unzipping the odt file, cut out the normal text tags and add one extra tag in the end. It shows two images with the 1000 images bug. The file can be opened in Firefox.
This bug is connected to bug Bug 89615 - FILESAVE: Writer saves invalid XML (style tag has two office:name attributes)
Created attachment 121385 [details] Multiple generated picture elements Record changes on.
Windows10 LibreOffice 5.0.2
(In reply to Aron Boss from comment #5) > This bug is connected to bug Bug 89615 - FILESAVE: Writer saves invalid XML > (style tag has two office:name attributes) Bug 89615 has been solved. So is your bug still present in an actual version of LO? => Set to NEEDINFO
I am running with version 5.3.1.2 on June 27th 2017. In this version the problem still occurs.
=> changed back to UNCONFIRMED
Aron: you never provided an example document. We cannot test anything with these XML files. I tried to reproduce from scratch, but there was no problem. I tried both replacing and deleting. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 98befbb26217b0bf3f35354e418a355280c52cfc CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 29th 2017
The problem is that the documents can't be put in the public domain. I can send you the document privately though.
(In reply to Aron Boss from comment #12) > The problem is that the documents can't be put in the public domain. I can > send you the document privately though. Then you need to create a minimal document with no sensitive information that shows the problem.
Uploaded a document with all letters changed to A whit the error. The error is not restricted to this document, that is, it is not a document error, but a program error.
Created attachment 134474 [details] Orginial documen. Will crash on demand after a recorded chang of text Just change some text around an image and record it. The recording will place multiple entries of the images in the document and therefore it will become unresponsive.
(In reply to Aron Boss from comment #15) > Created attachment 134474 [details] > Orginial documen. Will crash on demand after a recorded chang of text > > Just change some text around an image and record it. The recording will > place multiple entries of the images in the document and therefore it will > become unresponsive. I enabled Record changes and changed/typed text around the images on page 14 and 16. No crash. I saved the file under a new name and the file size is about the same as the original. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 98befbb26217b0bf3f35354e418a355280c52cfc CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 29th 2017
Well, in the document is an image multiple times. There will be no crash - only after adding notes in multiple layers by multiple writers- but there are multiple instances of a image generated. They can become very numerous and hence kill the machine because it takes a very, very, long time to process hundreds of images. The copies are generated when logging the changes. The exact trigger is not known to me.
comment #7 => W10 -> x86-64 (probably) Version 5.0.2
Please, could you describe a clear step by step scenario to reproduce the problem? Your comments #15 and #17 are contradictory. Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
Dear Bug Submitter, 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-20180903
Dear Bug Submitter, 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-20181009