Description: Open new spreadsheet, in the name box, enter something like A43:AMJ1048576 Then "Hide rows" Steps to Reproduce: 1.Open new spreadsheet, in the name box, enter something like 2.in the name box, enter something like A43:AMJ1048576 3. "Hide rows" Actual Results: Libreoffice hangs no dump Expected Results: Rows hidden Reproducible: Always User Profile Reset: No Additional Info: Also hangs in safe mode Worked in 7.1.4 Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
Repro Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded
Repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4debb7e8cc12563f46d1aaa58afdcb831f21cc83 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: CL
Uwe and Henrik, if you can repro with master, just mark New. If you cannot, you need to test back with reporter's version - if you can there, that's likely WFM. If repro with master, important is to see whether Inherited from OO or regression, so please test with OO and older LO. Finding exact LO branch (like 6.2) is necessary for most useful action, bibisect (even if you will not find it, mark BibisectRequest will get someone do it). It can also start im LO as ImplementationError or incomplete fix. Handling so many LO versions is easy in Windows with SI-GUI that downloads and extracts LO, without installation, so only disk space is required.
(In reply to Timur from comment #3) > Uwe and Henrik, if you can repro with master, just mark New. > If you cannot, you need to test back with reporter's version - if you can > there, that's likely WFM. > If repro with master, important is to see whether Inherited from OO or > regression, so please test with OO and older LO. Finding exact LO branch > (like 6.2) is necessary for most useful action, bibisect (even if you will > not find it, mark BibisectRequest will get someone do it). It can also start > im LO as ImplementationError or incomplete fix. > Handling so many LO versions is easy in Windows with SI-GUI that downloads > and extracts LO, without installation, so only disk space is required. Thanks for your advice. I'll try to mark bugs as new when they are reproduced with a master version.
But now, however, I ran the steps again and found that Calc doesn't hang. It just took a few minutes to process "Hide rows" but it eventually ended. So, no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4debb7e8cc12563f46d1aaa58afdcb831f21cc83 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: CL
And no repro in Version: 7.2.0.0.alpha1 (x64) / LibreOffice Community Build ID: 94c1521be4ef12f195d08413d5e2134e07a49f85 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: CL Not sure if this is a performance issue as it takes 2-3 minutes to process 1 million rows. I guess this is RESOLVED WORKSFORME.
I accept that this does not cause a hang, but the behaviour in 7.2 is so different from 7.1.4 that I think it counts a a bug. As well as "Hide Rows", inserting a cell takes a long time (about 10 seconds) as against instantaneous in 7.1.4. 7.2 is almost unusable for me. The status bar shows "adapting row height" for much of the time, even though I have only one sheet with fixed row height. Should I open a new bug report?
(In reply to David Lynch from comment #7) > I accept that this does not cause a hang, but the behaviour in 7.2 is so > different from 7.1.4 that I think it counts a a bug. > As well as "Hide Rows", inserting a cell takes a long time (about 10 > seconds) as against instantaneous in 7.1.4. > 7.2 is almost unusable for me. > The status bar shows "adapting row height" for much of the time, even though > I have only one sheet with fixed row height. > Should I open a new bug report? I think you should open a new bug report but do as you see fit.
(In reply to Timur from comment #3) > Uwe and Henrik, if you can repro with master, just mark New. > If you cannot, you need to test back with reporter's version - if you can > there, that's likely WFM. I'm a volunteer here and decide on my own, what I can do and what not. If it is not helpful, I'll stop adding my findings.
Opened Bug 144155 to rpelace this one.
(In reply to Uwe Auer from comment #9) > I'm a volunteer here and decide on my own, what I can do and what not. If it > is not helpful, I'll stop adding my findings. It is helpful. I thought you may proceed, but it's up to you. Thanks to all, issue was pinpointed. It's the same as reported, just precised, so it could've stayed here, just renamed. But now that new bug was opened, I'll close this one. NotaBug for hang.
*** This bug has been marked as a duplicate of bug 144155 ***