Created attachment 93953 [details]
Original CSV (an export from X-CART 4.4.5)
Problem description: Deleting a column from a specific document causes a crash
Steps to reproduce:
1. Import attached CSV with Character set "Unicode (UTF-8)", Language "Default - English (USA)", Separated by Comma, Text delimiter '"' (double quote) and all fields left at Standard for column type OR just open the ODS (it's the same thing saved in ODS, since LO will save the document fine)
2. Right-click the header of any populated column, select Delete Selected Columns
Hangs ?indefinitely? (15+ minutes, so I'll call it a crash)
Column is deleted in about 1 second (as 18.104.22.168 can do it about that fast, see below)
Operating system is marked "All" because I reproduced it on both Windows 7 Professional (64-bit) and Mac OS X (10.7.4) 32-bit application, both 22.214.171.124. This problem does not exist in Mac OS X, program version 126.96.36.199 as I tried the exact same thing without issue and it takes about a second like one would expect. I got a .hang report from the Mac, so that's included.
In case the attachments don't work, files are also at:
(Original CSV, an export from X_CART 4.4.5)
(ODS saved version after CSV import; LO saves the doc just fine)
(.hang report from the Mac)
Created attachment 93954 [details]
ODS saved version of the CVS
After importing the CSV, LO saves the file just fine, so here it is. I confirmed that using this file can reproduce the problem the same as doing the CSV import.
Created attachment 93955 [details]
.hang trace/dump from Mac OS X
I left the program for 15+ minutes before finally Force Quitting. This .hang dump was generated.
Hi Tim, it is not reproducible with:
Version: 188.8.131.52.0+ Build ID: 684a0308dcb847f816967202ba87f536b83dcb4e
TinderBox: Win-x86@42, Branch:libreoffice-4-2, Time: 2014-02-10_23:09:14
I think there were similar bugs, they were a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=72470, what I think is this.
Please if you are not agree, reopen it.
*** This bug has been marked as a duplicate of bug 72470 ***