When doing a document compare, the program gets a Fatal Error /!\ bad allocation. Happens with documents with 30 or so pages. Edit->Track Changes->Compare Document
no repro with Version: 6.2.0.0.alpha0+ Build ID: 58f2e4690b57f0fa7a95be3a023d54d8967f5529 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-08-23_23:45:59 Can you attach documents where bug occurs?
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Can't give a pair of documents to reproduce yet. None of the ones I've attempted to produce that are generic text have seen the issue. However, it has happened numerous times with several documents that I'm using which are about 40 pages to 50 pages and have hundreds of differences as an editor passes me changes that I want to verify/approve. As each change is accepted or rejected, Writer is very slow to go to the next entry. Then I have seen something just past (maybe a paragraph or two) that looks like !!! bad missing (or something close) then it hangs for a long time and eventually has to be killed. (Running on an I7 with 16GB of RAM and 1TB SSD, the slowness is not a hardware limitation.) It first happened on a daily build I'd installed. Then I completely uninstalled that version and reinstalled the release from scratch. Version: 6.1.0.3 (x64) Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-US (en_US); Calc: CL
Hello, Have you reproduced this problem again? If so, Did you get any crashreport ?
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-20190321
Dear robert, 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