Created attachment 107605 [details] An example .log file that causes my writes to become unresponsive Problem description: I have an application which creates .log files. These files only contain some text so nothing special. Opening them with textedit, notepad or Word is not an issue. It works fine. When I try to open them with libreoffice writer (V4.3.2.2) and they seems to have a certain size, it first ask in a window "import Dbase files" and which character set to use. After choosing the character set my libreoffice becomes not responding anymore and I need to force quit it. In libreoffice version 4.2.0.4 the same thing happens only I get an error message: Libreoffice 4.2 -Fatal error std::bad_alloc With smaller .log files which contain only few lines of text it works fine in writer. I have added an example .log file which causes a crash on my system: it contains 319 lines and has a size of 21kb
Hi Joren, Thanks to report this. I see the same behaviour (Fatal error, Bad allocation) with LO 4.3.2.2 and Windows 7 Home Prmeium. If I change file extension to .txt, there's no issue to open it. So I set Status to NEW and Hardware to All. Regards, Jacques
** 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.0.1 or preferably 5.0.2.2 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-10-14
Unconfirmed with v3.3.4 under windows 7 x64. Confirmed with v5.0.3.2 under mint 17.2 x64.
there's a single memory allocation of > 3gb in FResultSet.cxx:1289, that will never succeed on 32-bit. but the real problem is that the type detection thinks that this is a DBase file, when it's clearly not. can repro that in 4.1.0.4 already bibisect range: ee53857e984fea54b7dc08b99079b38766f0b796 153621f98ee98e4eacaebcf7d62f74d54755cab6 well that contains a lot of typedetection refactoring... fixed on master
Michael Stahl committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e3ff19b33c84557fd20e68960499933b4e52638 tdf#84834 sc: stricter type detection for dBASE files It will be available in 5.3.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.
Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-5-2": http://cgit.freedesktop.org/libreoffice/core/commit/?id=eb7364fffe39c1aecddcab6b9cf238475fa2013c&h=libreoffice-5-2 tdf#84834 sc: stricter type detection for dBASE files It will be available in 5.2.0.2. 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.
I just emptied that exact temp folder because my SSD was filling up inexplicably. By then the folder was up to around 150 gb. As I am writing this my "aria-debug-8328.log" in that https://www.essayswritingservice.co.uk/ folder has grown maybe 0.5 gb. It is now 26 gb large. This makes no sense to me. What the hell is going on