Steps how to reproduce with Version: 6.0.0.0.alpha1+ (x64) Build ID: a5af0fd9f27af42cf2e8571f659cdad6e606215b CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-07_00:30:02 Locale: de-DE (de_DE); Calc: CL: 1. Open attached "sample_001.ods" 2. Click A1 3. <ctrl-c> for copy 4. Click Column Heading "B" 5. <ctrl-v> for paste Expected: after few seconds paste is done, can continue editing Actual: hangs for a long time, with maximum CPU loac :-( I had to terminate LibO after 15 minutes or so a) All my tests seem to show that the problem is related to conditional formatting, other cells without c.f. do not show this problem b) Already REPRODUCIBLE with Version: 5.4.2.2 Build-ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU-Threads: 4; Betriebssystem:Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group c) all the same on WIN10
Created attachment 138229 [details] Sample Document d) With <https://bugs.documentfoundation.org/buglist.cgi?cmdtype=dorem&list_id=756719&namedcmd=DUPs114266&remaction=run&sharer_id=19321> I found possible DUP or related to "Bug 109280 - conditional formatting not preserved with copy paste operations"
e) Already REPRODUCIBLE with Version: 4.2.4.2 Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8 That underpins suspect concerning relation to Bug 109280 f) assigning a c.f. to a complete column via menu 'format → conditionla formatting' does not cause a problem g) I hope there is a workaround? In my universe a spreadsheet without possibility to spread c.f. to a whole column is completely useless. (d): Oops, related Bug or DUP is "Bug 103312 - Using format brush to copy conditional formats to some rows generates thousands (?) additional conditional formats making the spreadsheet unusable slow"
I can reproduce it back to Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) (oldest bisect max commit) but not in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=9ca02a663c3eee2698eb360dd5dc7afb1951e743..18e6e7d929c2be209407ed2e56b8ec4d5e6c4900
As expected still REPRODUCIBLE with Version: 6.0.5.2 (x64) Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard;
Seems quite fine with Version: 7.0.0.0.alpha0+ (x64) Build ID: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Dear Rainer Bielefeld Retired, 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
Tested on my PC with AMD Ryzen 5 3600 6-Core Processor / 3.60 GHz 16,0 GB: REPRODUCIBLE with Server Installation of Version: 4.0.0.3 WIN10 Build-ID 7545bee9c2a0782548772a21bc84a9dcc583b89; Special devUserProfile No longer reproducible with Installation of Version: 7.3.0.3 (x64) Build ID a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win | Locale: de-DE (de_DE); UI: de-DE | Calc: threaded | ElementaryTheme | My normal User Profile so WFM