This one is a spin-off from "Bug 34548 - EDITING: CRASH in action after Undo", created because fix for that Bug only works for crash proceeding as per original report, but not for crash as per Comment 22/23
Steps to reproduce with server installation of "Version 220.127.116.11.alpha0+ (Build ID: 576da8db5577f84d9c7e0e40ef3e166a7938c98) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-02-11_23:54:45" ENGLISH UI / German Locale on German WIN7 Home Premium (64bit) with own separate User Profile: als per Bug 34548 Comment 22/23
Currently it has not been checked when the bug has been introduced.
NEW due to results in Bug 34548
May be an additional backtrace can help to clarify whether this one is a DUO of "Bug 60786 - EDITING: CRASH after Edit Textbox after Undo"?
(In reply to comment #0)
> May be an additional backtrace can help to clarify whether this one is a DUO
> of "Bug 60786 - EDITING: CRASH after Edit Textbox after Undo"?
You want a bt also in the other bug?
@bfoman (In reply to comment #1):
We already have your bt for proceeding as per Bug 34548 C.19, so for Bug 60786 (what is for the remaining Crash for that proceeding) no more bt will be required.
It would be great if you could create a bt this bug here (means for Bug 34548 C. 22 and may be Bug 34548 C. 23), so that someone with skills can decide what are DUPs of what
Created attachment 74853 [details]
Bug 60787 - WinDbg session with FAILED_SOURCE_CODE
(In reply to comment #2)
> It would be great if you could create a bt this bug here (means for Bug
> 34548 C. 22 and may be Bug 34548 C. 23), so that someone with skills can
> decide what are DUPs of what
> 1. File> New> Presentation
> 2. Add some text in the Text Frame (where it says "Click to add title")
> 3. Deselect the Text Frame (for example click on "Click to add text")
> 4. Select the Title Text Frame (blue squares) and delete it
> 5. Undo
> 6. In the Task pane, try to change something, Layout, Master page...
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit
Crash on exit.
Attached full WinDbg session with FAILED_SOURCE_CODE.
This has again the same underlying cause as bug 34548 and is therefore fixed by the same patch.
*** This bug has been marked as a duplicate of bug 34548 ***