To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112605
------- Additional comments from [email protected] Thu Jun 24 08:35:16 +0000 2010 ------- ... somehow I have been added to this issue. Regarding remote references to (Uno) objects in the office process, it is either correct to * programmatically shutdown any remote bridges (including in process runtimes such as Java), or * to ensure that reachable objects are valid. We need to define the meaning of "file/exit" accordingly, as already suggested. The object life cycle in OOo is (partly) ref-count based, objects reachable are alive, objects becoming unreachable are (mostly synchronously) destroyed. Ideally VCL would follow this approach, e.g. create a "Display" with some controls on it, the controls hold references to the "Display", ensuring that it is kept alive at least wrt memory. Philipp is right about VCL's SolarMutex, the SolarMutex as well as VCL must not be in use after DeInitVCL (by they way, wasn't there any debugging aid to ensure this?). This bears the question what the sense of Tools SolarMutex is. Either use the VCL SolarMutex or the OSL GlobalMutex. --------------------------------------------------------------------- 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]
