142d3ec875
Erasing from data_ member maps can destroy contained Implementations, which in turn releases the UNO objects referenced from there, which in turn can cause XComponents to dispose, which in turn can call arbitrary code, so must not be done with rMutex locked. Witness the backtrace at <https://bugs.freedesktop.org/attachment.cgi?id=65142> linked from fdo#52639 (where this fix appears otherwise unrelated to that issue's main topic). Change-Id: If55a3841b761ec1d9a0ef61fe54784426c4ee442 |
||
---|---|---|
.. | ||
access_control.cxx | ||
bootstrap.cxx | ||
component.cxx | ||
component_context.cxx | ||
defaultbootstrap.cxx | ||
exc_thrower.cxx | ||
factory.cxx | ||
findsofficepath.c | ||
gcc3.map | ||
implbase.cxx | ||
implbase_ex.cxx | ||
implementationentry.cxx | ||
interfacecontainer.cxx | ||
macro_expander.cxx | ||
macro_expander.hxx | ||
paths.cxx | ||
paths.hxx | ||
propertysetmixin.cxx | ||
propshlp.cxx | ||
servicefactory.cxx | ||
servicefactory_detail.hxx | ||
shlib.cxx | ||
stdidlclass.cxx | ||
tdmgr.cxx | ||
typeprovider.cxx | ||
unorc | ||
unourl.cxx | ||
weak.cxx |