Apache OpenOffice (AOO) Bugzilla – Issue 7528
OLE Defect with ooowriter/ooomath
Last modified: 2003-09-08 16:56:16 UTC
When you enter many formulas in a ooowriter document, some (actually most) of the ooomath objects become broken. Instead of the entered formulas the icon for broken links is shown. This defect has also ocurred in build 641.
Kevin, thanks for taking the time to post this issue. Could you please attach all the files we need to reproduce this issue. Thanks.
Created attachment 2857 [details] A sxw document containing broken ooomath OLE Objects
The ooomath objects in the attached document were created by entering the math language directly into the document, selecting the line and pressing create>object>formula in the menu
Kevin, thanks for the attachment. I see 3 equations have a bad OLE link for me. Is this the same behaviour for you? Can you consistently reproduce this problem? Duplicated on Win NT 4.0 SP6a, OOo 1.0.1. I see 3 equations with an "puzzle piece" icon and the text "SvOutPlaceObject".
Thats the same picture for me. I can not consistently reproduce the problem because I did not yet figure out what the reason for the broken OLE Links is. It seems to happen randomly when working with many math objects. It is unclear why certain objects are concerned and others are not. But clear is, that the problem happens during the editing of the document. A correctly entered and showed formula stays correct after saving and reloading the document. The same applies for broken objects so I suppose it is not a problem in the saving process. You can actually produce big files with many formulas if you save the document everytime after entering a new formula and check all existing formulas before saving.
*** Issue 5043 has been marked as a duplicate of this issue. ***
Okay, here's the problem. The 3 objects that show up as broken links were never saved properly in the file. Normally the object should contain a directory and the appropiate XML files. In your test file, they end up being flat files. So we know why the file is broken, but that still leaves us with the problem of trying to reproduce this scenario that caused this bad file to be made. Kevin, do you have any additional comments? Unfortunately, if there is no consistent way to reproduce this problem, I'll have to close it as works for me. To the developers, is there debug info in the XML file assembly? I assumed no, but I never really tried hard to look at the entire zip file or take a look at the XML file specs.
Please look at the issue 11007 as well, I had almost the same probleme. Gabor
ES->MRU: the file may be broken (comments of PM) but it shouldn't crash when teasing a little bit the broken OLE in 644m8 -> VCL644MI! Region::Region(class Region const &) + 86 bytes VCL644MI! Window::GetPaintRegion(void) + 114 bytes GO644MI! B2dIAOManager::UpdateDisplay(void) + 77 bytes DL644MI! SdrDragView::BrkAction(void) + 22 bytes DL644MI! SdrCreateView::BrkAction(void) + 8 bytes DL644MI! SdrMarkView::UnmarkAllObj(class SdrPageView *) + 19 bytes DL644MI! SdrView::UnmarkAll(void) + 173 bytes SW644MI! SwFEShell::SelectObj(class Point const &,unsigned char,class SdrObject *) + 415 bytes SW644MI! SwWrtShell::UnSelectFrm(void) + 33 bytes SW644MI! SwEditWin::MouseButtonDown(class MouseEvent const &) + 3121 bytes VCL644MI! ImplHandleMouseEvent(class Window *,unsigned short,unsigned char,long,long,unsigned long,unsigned short,unsigned short) + 3245 bytes VCL644MI! ImplWindowFrameProc(void *,class SalFrame *,unsigned short,void const *) + 229 bytes VCL644MI! SalFrameWndProc(struct HWND__ *,unsigned int,unsigned int,long,int &) + 3455 bytes VCL644MI! SalFrameWndProc(struct HWND__ *,unsigned int,unsigned int,long,int &) + 1095 bytes VCL644MI! SalFrameWndProcW(struct HWND__ *,unsigned int,unsigned int,long) + 43 bytes USER32! 77e02e98() VCL644MI! SalInstance::Yield(unsigned char) + 128 bytes VCL644MI! Application::Yield(void) + 60 bytes VCL644MI! Application::Execute(void) + 34 bytes SOFFICE! desktop::Desktop::Main(void) + 3025 bytes
Reassigned to MRU
The crash will be fixed in OO 1.1 Beta2 (checked it with internal workspace sw011). The issue regarding the corrupted OLE objects (here: formulas) has been adressed in OO 1.0.2. But the documents which are already corrupted (like the attached) connot be displayed correctly anyway. The objects which do not show in there are destoyed and not repairable.
Closed.