https://bugs.documentfoundation.org/show_bug.cgi?id=103852
Michael Stahl <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Michael Stahl <[email protected]> ---
(In reply to Michael Meeks from comment #0)
> It seems to me that one 'obvious' fix here is to post the destruction of the
> XTransferrable from
>
> class CXTDataObject : public IDataObject
> {
> public:
> ...
> css::uno::Reference< css::datatransfer::XTransferable >
> m_XTransferable;
>
> To the main thread with an Application::PostUserEvent - which is commonly
> supposed to be thread-safe ;-)
yes that sounds reasonable, the good solutions are to delay the destruction
until the mutex in the clipboard thread is released, or move destruction to a
different thread.
it looks like there is no mutex in the clipboard thread? just a event loop...
that would make it more difficult... better to try your obvious solution.
> Alternatively - presumably dropping the SolarMutex as we go down this path:
>
> mergedlo!TransferableDataHelper::CreateFromSystemClipboard+0x94
> [c:\lo\libo-core\svtools\source\misc\transfer.cxx @ 2114]
>
> might work - at the cost of some significant re-enterancy hazard.
eeek. i don't like all those SolarMutexReleasers we currently have.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
