Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||OpenOffice should not hang when opening corrupted file|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description tuharsky 2004-07-28 13:43:42 UTC
I know it's a problem. But is it really unsolvable problem to make OOo a bit more proof to hanging opening corrupted files?
Comment 1 tuharsky 2004-07-28 13:44:31 UTC
Created attachment 16820 [details] File corrupted due to bad floppy
Comment 2 tuharsky 2004-07-28 13:51:37 UTC
Please remove the attachment, I shouldn't post it.
Comment 3 michael.ruess 2004-07-28 14:36:42 UTC
Somehow, an algorithm which catches such damaged RTF files and prevents a crash/loop.
Comment 4 tuharsky 2004-07-28 14:40:52 UTC
Please, are You able to delete the attachment?
Comment 5 aggro 2005-01-09 08:37:50 UTC
If I try to open attachment "corrupted.rtf" OpenOffice gives me error "Read-Error. File format error found at 168,262(row,col)." Microsoft Wordpad 5.0 seems to be able to open the corrupted file. I tried opening it by drag&drop from OO, since by default .rtf files are opened in different application. But... Version 1.9.65 crashes (sometimes closes without giving any information, sometimes notifies about an error) if I try to open a file which is created like this: - Create plain text file to desktop - Edit file to have two characters (I don't think the amount matters) "aa" in the content of the file. - Name file a.doc or any .doc name. I don't have any OO open (quickstarter can be open or not, doesn't matter), and I try to open the file on my desktop by double clicking it. OpenOffice closes and next time I start it, it askes if I want to send an error report, I sent one in hope it provides some extra information. OS: Windows 2000 + SP4, Finnish language version.
Comment 6 aggro 2005-01-10 21:32:58 UTC
Even while this seems to appear only with corrupted files, I think the priority for this bug should be raised to 2, because it fits in the "- Crashes in basic functionality". And I really think this should be fixed before version 2.0 is released, because software that crashes doesn't give a good image of itself. And as tuharsky has pointed out, this can appear in normal, real life situations also.
Comment 7 tuharsky 2005-08-22 11:53:36 UTC
Well, we can assume, that OOo would deal with many files that are uncorrectly named. M$O users (and OOo ones too) often don't recognize the filename extensions, and many old W3x programs and drives come with text files that have .doc extension. Some detection pre-import filter should take place that would test the header of opening file, and if the extension differs from assumed one, the OOo should notice user about bad format extension and ask for permission to change it. On export too.
Comment 8 michael.ruess 2009-10-27 13:06:40 UTC
*** Issue 106307 has been marked as a duplicate of this issue. ***
Comment 9 bettina.haberer 2010-05-21 14:54:31 UTC
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".