Apache OpenOffice (AOO) Bugzilla – Issue 9245
Writer freezes when trying to open Word Document.
Last modified: 2013-08-07 14:41:36 UTC
The attached document causes OOO Writer to totally freeze, when trying to open it. The document was created in Word 2000, and uses, for some odd reason, quite alot of text boxes.
Created attachment 3607 [details] Document that freezes OOO Writer
I can duplicate this bug on Win NT 4.0, OOo 1.0.1. When I opened this file in Word, it was O.K. However, opening it in Writer, it froze. I found the problem was in the text boxes. When I deleted all of the text boxes, it was O.K. to open in Writer. Even though remained only one text box, Writer became No Responding when opened it.
ES->MIB: still freezes in 644m8
Reassigned to MIB
Layout issue?
FME->CMC: There seems to be a wrong SwFmtVertOrient item. nYPos is LONG_MAX.
Well there are some ridiculously large location values set for some frames which are therefore displayed outside the page in word. The first one is the frame between the visible frame with 0 in it and the one with 20 in it. There is another frame there with "10" in it. Checking by exporting to rtf confirms that its location truly is (in twips) \shpleft2147461945\shptop2147409467\shpright2147462602\shpbottom2147410037 while the first one which has a negative left in it is \shpinst\shpleft-285\shptop34\shpright2937\shpbottom604. So this is the way the document actually is. I'm just passing on these huge values near LONG_MAX from the document itself.
FME: I don't have any idea what to do with this issue. Would you propose to handle these values in the filter or in the layout?
Well for 2.0 and msinteroperability we need to support the general issue of locations that are outside the page, e.g. if the values were 20000 twips vertically below the paragraph it would also be outside the page and we'd have to hold onto it. ibis #108749# is a similiar problem where a textbox is also positioned outside the page area. Is the hang here related to the huge number ? Word's UI restricts the values to be +-55,87cm i.e. SHORT_MIN/SHORT_MAX twips so I have no idea how this document came to exist. If the filter clipped the incoming values to this range would that help ?
FME->CMC: Yes, this would help.
FME->CMC: I think we should integrate the restriction of the values into the filter, not the core. What do you think?
Certainly, bounce it back to me then and for the 2.0 I'll restrict the values sent to layout to word's maximum UI values of SHORT_MAX/SHORT_MIN, and if that doesn't fix this then I'll pass it back :-)
FME: SHRT_MAX twips is only a couple of pages. Our layout should handle this correctly. Well, I hope so ;-)
accepted.
As discussed.
cmc->mmaher: As discussed.
accepted
Fixed in CWS limerickfilterteam08
fixed in limerickfilterteam08
Checked fix in CWS filter08.
Fix will be included in OO 2.0.
Hi, I found that this issue is Fixed, but target is OOo 2.0. Please consider to include this in OOo 1.1.1 if possible. Thankyou
o.k. in OO 2.0 snapshot src680m13.