Created attachment 69789 [details] .csv file 1.5 mb I have a normal .csv file that imports instantly and correctly on Libre office version 3.5.5 (default Mint 13 64 bit) and 3.5.7. Tested with both these versions. Tested in versions 3.6.3 and 3.6.2 , the same .csv takes 10 times as long to open and imports the data incorrectly.( Fields are all wrong and scattered) Attached is the .csv
Corrected description. Also preview area looks buggy, showing corrupted records somewhere from the middle.
Win7x64 Ultimate Version 3.6.4.1 (Build ID: a9a0717) Open without any problem, Space as separator. The first four columns as text. The last column as number US.
I think it might be an issue with the linux version - seeing that in Windows it works fine.
No, this is a cross-platform problem. Also, you don't have spaces chosen as separators by default, which is causing this.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Confirmed long initialization of preview. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 186f32f63434e16ff5776251657f902d5808ed3d TinderBox: Win-x86@39, Branch:master, Time: 2015-10-16_09:42:47 Locale: en-US (fi_FI)
Migrating Whiteboard tags to Keywords: (perf)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Confirmed long initialization of preview with Version: 5.4.2.0.0+ Build ID: 61d85c4e7c30ea0f5242d927b7456190020b4fbe CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group but not with Version: 6.0.0.0.alpha0+ Build ID: 41b7713334351d7cc455eef5241bd3988b9d1e94 CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-09-13_22:56:21 Locale: nl-BE (en_US.UTF-8); Calc: group
Created attachment 136530 [details] Callgrind output from 6.0 Still repro even with master. I compared 3.5 vs. master in Windows and 3.5 was definitely faster. If you repro multiple times with the same version, note that it remembers the chosen separator after import. The delay is only when Spaces are not chosen upon the summoning of the import dialog. Callgrind taken with: Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: a102f56123b5209a7dfaf33ba001433ec39d279f CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on September 25th 2017
Bibisect with Linux 43all points to range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=d31997559adac6f03d932cb6c5819149c38c1398...1856186951a70a0bcac4e0c3632ca4afe68c05e3 Out of which Eike's commit stands out: https://cgit.freedesktop.org/libreoffice/core/commit/?id=7928b651965f747b02593d2a9fc73fac7c86dbf5 commit 7928b651965f747b02593d2a9fc73fac7c86dbf5 (patch) tree 079cabd464d84456fc63a44849c402fee1ccd65b parent 95cc5de63b20c5986fe8f3913da86002eabd7cb1 (diff) resolved fdo#48621 better handling of broken CSV files * non-escaped (not doubled) quotes in quoted strings are regarded as broken representation and are taken literally, only a quote followed by a separator ends a field. If not being a separator themselves, trailing blanks between the ending quote and the separator are ignored, complementary to leading blanks between a separator and a quote. * quotes in a non-quoted string are taken literally Maybe a trade-off between speed and quality? :) Eike is already in CC
So yes, with Space not being set as separator for this data there's no field separation and the "relaxed quoting rules" try to combine lines for as the "one field" is regarded as broken/mis-quoted CSV data. Analyzing that mess takes more time than if the correct separator was already selected. Maybe some heuristic analysing the first two lines to detect a possible separator if none encountered could help.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=c807e7ea7a0725a4d8375eda07d6f70870e0d50a Resolves: tdf#56910 detect a Space (blank) separator if not selected It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Pending Jenkins for 6-1 https://gerrit.libreoffice.org/56814
Preview is now fast, cheers. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: c807e7ea7a0725a4d8375eda07d6f70870e0d50a CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on July 2nd 2018
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=33b7319e2e08812a2f7d3126e4b1ec90875d6165&h=libreoffice-6-1 Resolves: tdf#56910 detect a Space (blank) separator if not selected It will be available in 6.1.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.