Hi @jean, thanks for reporting.

With Win10x64
Version: 5.0.4.1 (x64) Build ID: 2def61bcbb29a7a8611b833682fe1291910b11ad-GL

about a couple of minutes, what seems too long. The strange is that seems the replace is done quickly but then takes a lot of time to finish.

Anyway you can import the data with the correct comma in two ways:

- Select as language in the import English (UK).
- Click on the head of first column with data and while Shift key is pressed click on the head of last column with data, after that on Column type select English (US).

I do confirm this bug still exist with Fedora 25 and LibreOffice 5.2:
Version: 5.2.3.3
Build ID: 5.2.3.3-11.fc25
Threads CPU : 8; Version de l'OS :Linux 4.8; UI Render : par défaut; 
Locale : en-US (fr_FR.UTF-8); Calc: group

If you do not click anywhere, it's a performance issue, it doesn't crash.
If you click a little bit on screens/content, it crash the software.

Continues to be a problem in 5.3.0.3 on Manjaro.

This was reported in Linux but it's also Windows. 
I see Calc was very slow with LO 5.0 but it's better with current LO, I tested master 6.5+. I see Search Results very fast, but still some "not responding" when I try to close it.

Slow replace is many times reported, I put some in See Also.
General impression is that it was fast before (like LO 3.5) than very slow (like LO 4.2) and that's it somewhat slow now. 
As written in https://bugs.documentfoundation.org/show_bug.cgi?id=83141#c12 
From 6.3 Search Results can be disabled but doing so doesn't help in this case. As explained, Search Results is quickly shown and sluggishness comes after.

Maybe we can keep open, to find out where "not responding" comes from.

The problem arises in [1] where all the found cells will be marked which takes time for 6974 cells. We may limit the selection which should increase the performance?


[1] https://opengrok.libreoffice.org/xref/core/sc/source/ui/view/viewfun2.cxx?r=ef38b9af#2030

Imho, in both cases (Bug 96290 and Bug 123461) the culprit is ScRangeList::Join which tries to join the marked ranges. It holds a list of ranges and checks if it can join with the found one, otherwise it adds the new created ranges and continues to join the remaining ranges from the search result.

The internal data structure is a vector and the data is as follows:
[0] = {aStart={nRow=1 nCol=1 nTab=0 } aEnd={nRow=2 nCol=1 nTab=0 } }
[1] = {aStart={nRow=4 nCol=1 nTab=0 } aEnd={nRow=6 nCol=1 nTab=0 } }
[2] = {aStart={nRow=9 nCol=1 nTab=0 } aEnd={nRow=15 nCol=1 nTab=0 } }
[3] = {aStart={nRow=18 nCol=1 nTab=0 } aEnd={nRow=20 nCol=1 nTab=0 } }
[4] = {aStart={nRow=22 nCol=1 nTab=0 } aEnd={nRow=24 nCol=1 nTab=0 } }
[5] = {aStart={nRow=26 nCol=1 nTab=0 } aEnd={nRow=26 nCol=1 nTab=0 } }
[6] = {aStart={nRow=28 nCol=1 nTab=0 } aEnd={nRow=29 nCol=1 nTab=0 } }
[7] = {aStart={nRow=32 nCol=1 nTab=0 } aEnd={nRow=35 nCol=1 nTab=0 } }
[8] = {aStart={nRow=37 nCol=1 nTab=0 } aEnd={nRow=37 nCol=1 nTab=0 } }
[9] = {aStart={nRow=40 nCol=1 nTab=0 } aEnd={nRow=42 nCol=1 nTab=0 } }
[10] = {aStart={nRow=44 nCol=1 nTab=0 } aEnd={nRow=55 nCol=1 nTab=0 } }

The algorithm always loops over all ranges to check whether a range can be joined or not. A new range may look like the following:
rNewRange = {aStart={nRow=66 nCol=14 nTab=0 } aEnd={nRow=67 nCol=14 nTab=0 } }

In the end it gets even worse, because if a range can be joined, the function tries to join the newly created range as well. In this case, the range contains about 6974 ranges which leads to this performance issue.

Imho, a vector of ranges maybe the wrong data structure when there a fast access is needed.

So either we show only around a 1000 marked ranges, or we have to think about a better algorithm which can join ranges faster :(

Dear jean-baptiste,

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