To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62088
User as changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Feb 16 04:10:26 -0800
2006 -------
The problem behind:
Closing any resource inside OOo isnt an easy job always. Often enoughh we make
it asynchronous. E.g. our menus had problems on synchronous closing frames ...
our our test tool had problems on terminating the office synchronous.
Normaly the dispatch ".uno:closeFrame" used here is implemented asynchronous.
Internaly it calls ((XClosable)xFrame)->close().
But now two dispatch interceptor objects are involved. And one of them calls
close() synchronous. But this will close the same frame which stands on the
same
stack (some levels above) in another interface method windowClosing().
That's the reason why this frame blocks the whole thread. It waits for
finishing this
API call. I've implemented it a little bit more gracefully. Because the
intention of
windowClosing() is clear. So windowClosing can supress setting this lock ...
and
Frame->close() will work.
BUT: Now it depends from all implementations available on the same stack. If
only
one of these methods make a call after close() it can lead in potential crash.
The current version of OOb680 does not have a problem. But every added line to
the involved code can break this ! Be warned .-)
---------------------------------------------------------------------
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]
