Bug 90226 - EDITING, UI : Using autofilter on large files causes all calc menus/popups to be displayed incorrectly
Summary: EDITING, UI : Using autofilter on large files causes all calc menus/popups to...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) Master
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
Keywords: bibisected, regression
Depends on:
Blocks: VCL-Scheduler Main-Loop
  Show dependency treegraph
Reported: 2015-03-25 12:45 UTC by Dennis Francis
Modified: 2021-06-29 03:49 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:

sample csv file on which the problem can be reproduced. (239.09 KB, text/csv)
2015-03-25 12:45 UTC, Dennis Francis
printscreen of bug (141.21 KB, image/png)
2015-03-25 18:11 UTC, raal

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Francis 2015-03-25 12:45:03 UTC
Created attachment 114335 [details]
sample csv file on which the problem can be reproduced.

Steps to reproduce

1) Open the attached csv file from Calc **build from the latest master branch**
2) Go to Data > Filter menu and click on Autofilter.
3) Invoke the autofilter popup for the column "awardID"
4) Uncheck the checkbox corresponding to "Baseball Magazine All-Star" and 
   click ok.
5) Now immediately invoke any menu/auto filter popup/right click context menu, (none of them displays properly for me).

Also noticed that this behavior does not seem to occur for smaller files.

I also tried to do the same in Calc 4.3.6 but could not reproduce, so I think this is a regression.

The attached file was obtained from : http://seanlahman.com/files/database/lahman-csv_2015-01-24.zip
Comment 1 raal 2015-03-25 18:11:43 UTC
Created attachment 114340 [details]
printscreen of bug

I can confirm with Version:
Build ID: c3087d969671e62182eb049850479e77190ccff4
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-03-22_04:37:00
Comment 2 Matthew Francis 2015-03-26 05:52:50 UTC
Bibisect results from 45 dbgutil:
 0d45a5d167c62cde4d7f1a76b2bed58c118cfb7d is the first bad commit
commit 0d45a5d167c62cde4d7f1a76b2bed58c118cfb7d
Author: Miklos Vajna <vmiklos@collabora.co.uk>
Date:   Sat Mar 7 05:48:46 2015 +0100

    2015-03-07: source-hash-333f8a76341f5b4921e89012d133007503e49612

So this is most likely more fallout from the timer/idle work

Adding Cc: to tobias.madl.dev@gmail.com; Any ideas about this one?
Comment 3 Matthew Francis 2015-04-15 02:32:27 UTC
Confirmed that this is from the range (not individually buildable)

i.e. the timer/idle series
Comment 4 Robinson Tryon (qubit) 2015-12-13 11:12:18 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2017-09-14 10:30:30 UTC
Removing the 'bisected' keyword.
Comment 6 QA Administrators 2019-08-19 07:01:14 UTC Comment hidden (obsolete)
Comment 7 Kevin Suo 2020-11-29 14:34:12 UTC
I do not reproduce with the recent 7.1 beta version. Set status to NEEDINFO.
Dennis: could you please retest?
Comment 8 QA Administrators 2021-05-29 04:53:18 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-06-29 03:48:59 UTC
Dear Dennis Francis,

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