Apache OpenOffice (AOO) Bugzilla – Issue 14046
After doing UNDO in ms word document OO crashes
Last modified: 2013-08-07 14:44:28 UTC
If I do Arrange -> Send to back the picture which is imported on the front and has to be on the back and then do UNDO OOo crashes.
Created attachment 6016 [details] ms word document which crashes after UNDO
Created attachment 6017 [details] ms word document which crashes after UNDO
I couldn't see the image you were talking about, but I clicked on the first page, did send to back, and undo, and boom! just like you said. Reproduced on ooo1.1beta1 on Red Hat 8 x86.
Created attachment 6111 [details] symbolic stack dump of crash caused by SendToBack followed by Undo
Created attachment 6135 [details] valgrind log of reproducing error with ooo644_m11 on red hat 8
unfortunatly too late for beta2, retarget to RC, raising prio to 2 because of crash.
Created attachment 6167 [details] Stack dump of first indication of trouble under valgrind. Interesting.
Reassigned to MRU
MRU->DVO: There's a graphic which spreads over the whole page. Select this, send it "to back" (z-order) and Undo -> crash.
dvo: Fixed in sw015 (for OOo 1.1, release), sw/../edundo.cxx The problem was in SwEditShell::Undo(..). After successful undo drawing objects were selected (if appropriate), but the selection code directly accessed the drawing layer (rather than going through the Writer shell), thus causing an inconsitency in the current selection. Now, SwFEShell::SelectObj(..) is called, so drawing objects are now selected in the same way that a mouse click would select them. The stack traces turned out to be a bit misleading in that they showed a follow-on problem, after the original point of failure. But with the document the problem was easily reproducable, so I think I got the bug down alright.
This bug is related to issue# 14045, as in the original MS Word document the picture (a graphic which spreads over the whole page) is on the back, just OOo 1.1 displays it on the front (OOo 1.0.2 displays the graphics correctly - on the back). It would be just great if issue #14045 was solved together with this bug ;).
dvo->egle: No, it doesn't to solve the #14045 problem. What I fixed here was a crash in the undo mechanism, and will not affect the loading. At first view, #14045 seems to be an import or an UI issue, neither I which I know a whole lot about. :-)
dvo: Ughh, my fix worked for Undo, but the same problem was in Redo as well. I found out only now, so the complete fix will be in sw016, not sw015.
dvo->mru: Works in sw017. Please verify & close.
Checked fix in CWS sw017.
Verified fix with internal CWS sw017. Fix will be available in OO 1.1.
Fix applied to OO 1.1 RC.