Bug 353988

Summary: Text to columns hangs when done twice.
Product: [Applications] calligrasheets Reporter: bat cooper <bat>
Component: functionsAssignee: Calligra Sheets (KSpread) Bugs <calligra-sheets-bugs-null>
Status: REPORTED ---    
Severity: normal CC: mecirt
Priority: NOR    
Version First Reported In: 2.9.2   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: File of characters to be split into columns delimited by spaces.

Description bat cooper 2015-10-16 23:26:22 UTC
Using the text-to-columns option more than once causes it to go into an infinite loop using all the CPU time so Sheets has to be killed with task manager.
Comment 1 bat cooper 2015-10-16 23:27:53 UTC
If you restart the program and repeat the operation, it still hangs.
Comment 2 Tomas Mecir 2015-11-28 17:40:37 UTC
I am unable to reproduce this problem on the latest git version. If you are getting the issue on that as well, please include the exact steps to reproduce this problem. Thanks!
Comment 3 bat cooper 2015-11-28 22:25:38 UTC
Created attachment 95793 [details]
File of characters to be split into columns delimited by spaces.

Hello Tomas, I compiled 2.9.9 Sheets and it does the same thing for me but I should say that this problem only seems to happen if you have a long string of text to be split up into columns e.g. I found that with the attached file, I can paste the contents into a cell and then do text-to-columns, delimited by spaces and Sheets still hangs on the first or second time you try. It works OK if you go Insert -> External Data -> From Clipboard, so the problem is just when the string is initially pasted into one cell and you try Data -> Text-to-Columns. It works fine with shorter strings, so I may just be giving it too much at once!! Thanks for looking at this!
Comment 4 Justin Zobel 2021-03-09 22:43:36 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.