Apache OpenOffice (AOO) Bugzilla – Issue 103507
Crash with too large paragraph format
Last modified: 2013-08-07 14:44:00 UTC
OpenOffice 3.1 crashes closing a file (RTF or ODT) with a strange paragraph format. This paragraph has very large width with hidden beginning and ending impossible to corrected this width. My method : I opened the RTF file that I received. I closed this file. OpenOffice crashed. This is always reproducible. I reopened this RTF file. I copied and pasted an embedded paragraph in a frame in a new file named essai.odt. This paragraph (not the frame) have very large width which is impossible to modify. The content of the paragraph is editable but the beginning and the end are invisible. I saved essai.odt. I closed the window of essai.odt. OpenOffice crashed. The file essai.odt is readable without other issue and can be saved. But OpenOffice always crash when this file is closing.
Created attachment 63515 [details] The file that crashed OpenOffice 3.1
Issue is confirmed
Created attachment 63523 [details] Report crash. OOo-Dev_OOO310_m15
I checked with "Ooo 3.1.0 WIN XP multilingual version English UI activated [OOO310m11 (Build 9399)]" and can confirm the reported crash. Steps to reproduce: 1. Open attached essai.odt 2. Save as essai1.odt 3. Close Document window expected: only that window will be closed actual: crash Unfortunately my OOo did not create a crash report
@MBA: please reassign to the suiting developer. Reproduced on SunRay with current DEV300m52. -> OS/Platform = All. Not reproducible in 3.0.1 -> regression.
After some reaserches, duplicate of issue 101239. *** This issue has been marked as a duplicate of 101239 ***
Closed
@es : Why do you say that this issue is fixed ? How this issue is the same that 101239 which was marked fixed ? I tried OOo 3.2 (DEV300 m51) and this issue is not fixed in and is always reproducible. Should I reopen it ?
Issue 101239 is fixed, but the fix is currently not available in a milestone build, it is only available in a "child workspace" that - after successful testing - is integrated into our master code line. So please be patient. I added a comment to issues 101239 that your scenario should be tested if possible so that we can verify that this issue indeed is a duplicate.