Created attachment 136650 [details] Graph to copy-paste The initial report is below. Now I can reproduce the crash with 5.4.1 but the memory consumption is still huge (1.5 Gb) when I copy and paste or scroll the ODT with the graph. ------------------------------------------------------------------------- From: Landry MINOZA <landry.minoza@musee-orsay.fr> To: submit@bugs.debian.org Subject: [libreoffice] Writer takes 100% cpu and is extremely slow when a copy/pasted graph from calc is on the screen Date: Mon, 16 Jan 2012 10:29:00 +0100 [Message part 1 (text/plain, inline)] Package: libreoffice Version: 1:3.4.4-2+b1 Severity: important --- Please enter the report below this line. --- When I create a graphic in clac, copy it and paste in writer, writer becoms extremely slow, taking 100% CPU. It takes approximately 30s between ech character of text I enter. If the graphic is not on the screen anymore (after inserting a page break for exemple, It becomes as responsive as usual. Tested on 2 amd64 SID, also tested with 3.5beta2 from experimental. When I tried on the sames versions of libreoffice on Windows (both 3.4 and 3.5 on XP and 7 32bits) it was a little slower than usual but usable. I attached some test files.
Created attachment 136651 [details] ODt sample for pasting the graph
> The initial report is below. Now I can reproduce the crash with 5.4.1 but > the memory consumption is still huge (1.5 Gb) when I copy and paste or > scroll the ODT with the graph. I guess you meant "I can't reproduce the crash"? I can't reproduce the slowness described in Version: 6.0.0.0.alpha0+ Build ID: 13df3777e4b6ff7537692b396be67a5fd2b9b001 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Yes, I can't reproduce the crash. Ok, I will try with the daily build.
(In reply to Stéphane Aulery from comment #3) > Yes, I can't reproduce the crash. > > Ok, I will try with the daily build. Hello Stéphane, Have you had the chance to test it in a daily build?
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-20180530
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-20180703
No crash since LO 5.4.1-1 No slow response since LO 6.0.x
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.
Can I found a portable version of the last buil for windows?