I've been working on a document with a significant number of line art objects (that is, art composed of drawing objects, not imported bitmap images). As the number of objects increases, using Writer to work on the document slows, but more critically, above a certain threshold of objects, Writer freezes/crashes altogether when saving the document. So far, I've only been able to reproduce this on Windows (one 32-bit Win7 system, one 64-bit Win7 system), but not on Linux (running LO 5.0.3 on Mint). I've attached a small ODT file that can be used to reproduce this issue. The file (Too Many Images.odt) is simply one page of all the images in our original document (grouped together for convenience). To reproduce, I repeatedly copy the object group, paste it onto the next (blank) page, and save. Typically, Writer freezes/crashes when trying to save after page 9 or 10 of this routine. Incidentally, if I create a document on Linux with 10+ pages of this object group, I can successfully save and open it, but if I open that file on Windows, then Writer freezes and crashes. By "freeze/crash", I mean that a blank dialog window quickly opens and disappears and the main window graphics/text/toolbar is distorted or blank. Playing around at this stage reveals that the otherwise unresponsive window can be closed by pressing the Esc key, after which the application crashes altogether.
Created attachment 126900 [details] One page of many graphics
I can also reproduce this error (and originally encountered it, actually) when adding sub-documents to a master document. In that scenario, adding this document file to a master document, then saving, then repeating also eventually leads to a freeze/crash. But my original bug report was aimed at keeping it simple; I assume if the issue involving copy/paste can be fixed, it will also resolve the scenario involving master documents.
Yep, I can make it crash on Windows after reaching page 9 (paste, save, paste, save..). I used the drawing tool selection to select them. It seems I am unable to get a useful backtrace. Let's hope builds from tinderbox 39 resume as they contain debug symbols. Win 7 Pro 64-bit Version: 5.3.0.0.alpha0+ Build ID: ba269f7294e2416659011cbb498a2c6b5f9d5199 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-09-12_02:36:16 Locale: fi-FI (fi_FI); Calc: CL 4.3.0.1
I may be wrong, but I can't repro with 5.4+ on Windows.
(In reply to Timur from comment #4) > I may be wrong, but I can't repro with 5.4+ on Windows. I can still repro with Win 10 Version: 5.4.0.0.alpha0+ Build ID: 1c27286b9d5331634c073cd3e327bd941e61bbb6 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-01-23_03:24:17 Locale: fi-FI (fi_FI); Calc: group I will try TB39 build with debug stuff.
Created attachment 130893 [details] Backtrace of crash with 5.4 Version: 5.4.0.0.alpha0+ Build ID: c2850bab4f7e5700151a18d806268f2b86a25d56 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-01-24_03:10:33 Locale: fi-FI (fi_FI); Calc: group
** 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 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
Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-AU (en_AU); Calc: CL Works for me, tested up to 20 pages of the images.
It's true, I can't repro this anymore. It doesn't seem to be about 32-bit vs. 64-bit as the memory used was still only 277MB after 11 pages of pasting. Version: 6.1.0.0.alpha0+ (x64) Build ID: 77db2da61658906c354084b13a95f1102949fbd0 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-03-04_22:51:24 Locale: fi-FI (fi_FI); Calc: group