In Calc, when I perform AutoFilter on a column with large number of distinct values (almost 30,000 values), it takes forever, in certain condition, to generate the dropdown list. On another machine, the dropdown list is generated in a few seconds (less than 5 seconds, which is very acceptable). I compared the two machines found that the Windows 7 performance option named "Use visual styles on windows and buttons" is different on the two machines. (You can find this setting in System Properties -> Performance Options.) With the option turned off, the AutoFilter dropdown list is generated fast. With the option turned on, it is never generated successfully with 30,000 distinct values. Can this be fixed? Most Windows 7 users leave this performance option turned on by default. Note: This problem does not occur in Windows XP even if the visual setting is turned on.
Created attachment 67604 [details] Sample Document NOT reproducible with Server Installation of "LibreOffice 3.6.2.1 rc English UI/ German Locale [Build-ID: ba822cc] on German WIN7 Home Premium (64bit) and attached sample document. I clicked the Filtr3 button, Standard Filter, Condition "Filter3 = 12345", works fine with "Use visual styles on windows and buttons" active @Reporter: Any Ideas?
Created attachment 67633 [details] This document should be able to reproduce the problem With Windows 7 "Visual styles" turned off, performing AutoFilter on all columns is all right although the hourglass may appear for a few seconds. With the setting turned on, AutoFilter on col1 will make Calc hang. I waited for 5 minutes and the AutoFilter popup appeared. But when I clicked an item in the list, it hanged again. I decided not to wait and kill the app.
The document I attached will reproduce the problem. Turn off the "visual styles" first and test AutoFilter on col1. It should work with some lag. Then "turn on" the setting and test AutoFilter on col1 again. Calc should hang. I tried to figure out the condition. This situation should be true. Please verify it. *All* of the following condition must be true to reproduce the problem. 1. Windows 7 "visual styles" is turned ON. 2. The column to apply AutoFilter must contain Unicode characters. (I tested English alphanumeric. Calc did not hang.) 3. The average length of data in the column should be large. (10 chars does not make the problem. 100 chars makes the problem.) 4. The number of distinct values of cells that contain Unicode characters should be large. (I tested long data but with only 100 distinct values. No problem.) I hope you can reproduce it. Thanks.
(In reply to comment #1) > Created attachment 67604 [details] > Sample Document > > NOT reproducible with Server Installation of "LibreOffice 3.6.2.1 rc > English UI/ German Locale [Build-ID: ba822cc] on German WIN7 Home Premium > (64bit) and attached sample document. > > I clicked the Filtr3 button, Standard Filter, Condition "Filter3 = 12345", > works fine with "Use visual styles on windows and buttons" active > > @Reporter: > Any Ideas? Have you looked at the attached file?
Hello I reproduce the bug with Version 3.6.2.2 (Build ID: da8c1e6) & Windows 7 64bit and your file (with-unicode-chars.ods) but not all columns: on Column A specially (col1) I suspect, therefore, that the type of character is concerned. I replaced the non-Latin characters with numbers and copied and pasted the data for approximately 120,000 lines. With this file I do not reproduce the bug. Regards Pierre-Yves
(In reply to comment #5) > Hello > > I reproduce the bug with Version 3.6.2.2 (Build ID: da8c1e6) & Windows 7 > 64bit > and your file (with-unicode-chars.ods) but not all columns: on Column A > specially (col1) > > I suspect, therefore, that the type of character is concerned. > > I replaced the non-Latin characters with numbers and copied and pasted the > data for approximately 120,000 lines. With this file I do not reproduce the > bug. > > Regards > Pierre-Yves Thanks for your response. Since we know how to reproduce it, should this issue's status changed from Unconfirmed to something else?
(In reply to comment #6) > Since we know how to reproduce it, should this issue's status changed from > Unconfirmed to something else? I believe so, sorry this is an oversight on my part ... Regards Pierre-Yves
please retest with current LibO 4.3.2.2 and give an update of the bug status, if still reproducible or not.
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** 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.1.6 or 5.2.3 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-20170103
Dear preechaw, 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
still repro with 6.2.8.2 and 7.0.0.0.a1+, besides frustration about 8 year old bugs ... for this case i'd say: forget about such windows style gimmicks ... Version: 7.0.0.0.alpha1 (x64) Build ID: 6a03b2a54143a9bc0c6d4c7f1... 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: threaded
Windows 7's end of life was early 2020. I understand that many users will be stuck with Windows 7 for while, possibly years, but do we need to keep this one open, as it is very unlikely it will attract attention and get fixed? Not sure if there are guidelines around operating system EOL in the LO project. https://www.microsoft.com/en-US/windows/windows-7-end-of-life-support-information
Hi (In reply to stragu from comment #13) > Windows 7's end of life was early 2020. I understand that many users will be > stuck with Windows 7 for while, possibly years, but do we need to keep this > one open, as it is very unlikely it will attract attention and get fixed? > Not sure if there are guidelines around operating system EOL in the LO > project. Well, I no longer reproduce the bug on Windows 7 (with "Use visual styles on windows and buttons" on) & Version: 7.1.4.2 (x64) / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded So... I would therefore agree to close this bug, but I am not the reporter. Bests regards Pierre-Yves
Close as WORKSFORME per comment 14. Even if it was not the case, this is now not an issue as the autofilter is now instant per various improvements these days on master, see bug 133835. Those who are affected by the slowness are encouraged to use a daily build (after the end of today, maybe tomorrow) to test and find regressions.