Problem description: bug with clipboard Steps to reproduce: 1. Open document with 70000-80000 lines 2. Mark all (Ctrl+A) 3. Copy in clipboard(Ctrl+C) 4. Close document. Current behavior: LibreOffice closed, but he is running in processes and load 100% 1 core CPU Expected behavior: Platform (if different from the browser): Windows XP(32 bit) Browser: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0
Tested in 3.6.1.2 (Windows)
Problem has fixed not properly. Steps to reproduce: 1. Open document with 70000-80000 lines 2. Add autofilter->Standart Filter->field>0 2. Mark all (Ctrl+A) 3. Copy in clipboard(Ctrl+C) 4. Close document. Current behavior: LibreOffice closed, but process(calc) is running and load 100% 1 core CPU and clipboard in windows does not work. Tested in 3.6.1.2.
Andrey, please attach a test file. Is this bug still valid / reproducible with the latest LO release? Currently 4.2.0.4: http://www.libreoffice.org/download/ Please also try resetting your user profile and let us know if that helps: https://wiki.documentfoundation.org/UserProfile Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME. Setting to NEEDINFO until more detail is provided.
Created attachment 93901 [details] Test File for check this bug Bug is confirmed on LO 4.1.4.2 On version LO 4.2.0.4 I have not seen the dialog box for selecting of "Standard filter" to choose the value ">" 0(zero) in the field "balances" But I waited 40 minutes!!! And then i killed the process manually in task manager. Resetting the profile did not help.
Version is oldest version not newest. Is this still an issue? If so - andrey, any thoughts?
Version 4.3.3.2 Things got even worse. Now the application is not closed.
@andrey: pls don't change the version to a newer one :) (Read the note that appears when you change that field :p )
Cannot reproduce with LO 4.4.3, win7
(In reply to andrey from comment #2) > Problem has fixed not properly. > > Steps to reproduce: > 1. Open document with 70000-80000 lines > 2. Add autofilter->Standart Filter->field>0 > 2. Mark all (Ctrl+A) > 3. Copy in clipboard(Ctrl+C) > 4. Close document. > > Current behavior: > LibreOffice closed, but process(calc) is running and load 100% 1 core CPU > and clipboard in windows does not work. > > Tested in 3.6.1.2. Hi, Not reproduce with LO 4.4.5.1 / LO 5.0.0.3 and file balances2.ods Win7/x86, cpu 2,5 Ghz, ram 3 Go Bernar
Andrey: please test with 4.4 and/or 5.0. Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Just I checked on 5 version. The error remained.
Created attachment 117713 [details] This video shows the process of how it happens This video shows the process of how it happens
The bug tdf#93423 seems to give ground to this report :)
> Problem has fixed not properly. > > Steps to reproduce: > 1. Open document with 70000-80000 lines > 2. Add autofilter->Standart Filter->field>0 > 2. Mark all (Ctrl+A) > 3. Copy in clipboard(Ctrl+C) > 4. Close document. > > Current behavior: > LibreOffice closed, but process(calc) is running and load 100% 1 core CPU > and clipboard in windows does not work. > > Tested in 3.6.1.2. Can confirm bug present in LibreOffice version 5.0.4.2 build id 2b9802c1994aa0b7dc6079e128979269cf95bc78 using Win10. After Ctrl+C and closing the LibreOffice window the task remains running at 100% on one core. Used the provided test file.
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
The bug is present in LO 5.3.0 x86 version on Windows 7 x86 with all updates.
Setting Assignee back to default. Please assign it back to yourself if you're still working on this issue
** 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
Dear andrey, 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 https://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
as of today with below ver. i'd say WFM, copying the cells threw the cpu-load to ~17% for some minutes ~3, (equaling ~100 on a 1 core system) after some time it reduced to 7%, and fell back to 2% - idle - on closing just that window, other calc instances still open ... if you consider significand load for some time ok, then ok, if you say it's a mem to mem copy and shouldn't last more than a second ... still bug, Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6e6e531b564cdc9d5b25287c215cdc5a1fcbb346 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL
Dear andrey, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug