To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105557 Issue #|105557 Summary|[sw] unocore: no destructor locking Component|Word processor Version|DEV300m60 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|programming Assigned to|mst Reported by|mst
------- Additional comments from [email protected] Fri Oct 2 14:00:48 +0000 2009 ------- locking of UNO implementation in writer is completely broken in one aspect: destructors the destructors of UNO objects are invoked from remote bridges when the remote side no longer references the UNO object. currently, most UNO objects in writer do not do any locking. worse, simply putting in a SolarMutex guard does not help: the guard will be dropped before destructors of base classes and members are invoked. possible solutions: 1. make all potential base classes threadsafe 2. prohibit non-threadsafe base classes, and introduce pImpl objects that then derive from the non-threadsafe base classes. the UNO object destructor locks SolarMutex and explicitly deletes pImpl (auto_ptr does not work!) 3. wait for the mythical threading framework to solve all our locking problems... --------------------------------------------------------------------- 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]
