To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73201





------- Additional comments from [EMAIL PROTECTED] Wed May  9 14:42:00 +0000 
2007 -------
The today's deeper investigation opened my eyes:
I've found the Writer fly frame, which is anchored inside the page footer -
somehow in January my eyes must be close.
I reproduced the given stack under Windows with enabled accessibility support
with another document. The creation of this document was possible, because I've
figured out, that under a certain condition the accessibility object for the
Writer fly frame wasn't disposed during the destruction of the Writer fly frame.
Thus, an accessibility event for this Writer fly frame was still queued. The
processing of this queued event afterwards accessed the *destroyed* Writer fly
frame. That, what CMC already found out.

I think, the provided patch will work. But, it's the wrong way. It was intented,
that the processing of the accessibility events are postponed during the process
of the the internal action. Thus, it is no good idea to process these events
before each destruction of a Writer fly frame in destructor of <SwLayoutFrm>.
I will try to fix the root cause - the missing dispose of the accessibility
object of the Writer fly frame.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to