Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OpenOffice.org Writer crashes on opening a long document | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | Unknown <non-migrated> | ||||
Component: | code | Assignee: | eric.savary | ||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | OOo 1.0.0 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Unknown
2002-06-07 16:36:25 UTC
dvo: The crash occurs in the XMLParaContext destructor. ~XMLParaContext creates a text cursor over the current paragraph in order to set the paragraph's attributes; in this case XText::createTextCursorByRange fails and returns an empty reference -> GPF. The responsible implementation is SwXFootnote::createTextCursorByRange, so this happens while importing a footnote. The problem is apparently in unoftn.cxx#463. More specifically, the following check fails, aRef is not being assigned to and thus remains empty: if( aPam.GetNode()->FindStartNode() == pTxtFtn->GetStartNode()->GetNode()) aRef = ...; dvo->sba: I think TL should handle this. Please consider which version this should be targeted for. ES->DVO: that's great how you cab get stack only looking at a proble description ;-))). To evaluate a target we need to know if this may happen to a lot of user, since when and so on. Well we need to have a *bugdoc* to can play with. You discretly ask for it, isn't it? So you can better decide how ro rate it. By default, it will be a OOo 1.1 Beta dvo->es: Oops, I had forgotten about this one. I had indeed asked the submitter for a bugdoc, which he promptly supplied. Added was a comment stating asking for confidentiality which I think we should honour, which is why I haven't submitted it to IssueZilla and won't do so either. I also promised to delete it later, but luckily only did a half-assed job about it (I still have the original e-mail), so i can still reproduce the problem... :-) Either way: The bug still isn't fixed in the current build. Since I have a better understanding of these issues now, I have created a much smaller bug-doc showing the same problem. I will post that doc. The problem apparently occurs when a footnote contains a text section (at the end?). Created attachment 4521 [details]
A document with a section inside a footnote.
dvo: Fixed for OOo 1.1. Patch is in sw/source/core/unocore/unftn.cxx, sw006. dvo->tl: This is your turf; please review. . US->HBrinkm: as said reopened for verification and chown. . Ready for QA fixed verified Ok in 644m4s4 |