https://bugs.documentfoundation.org/show_bug.cgi?id=103515
Michael Meeks <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #2 from Michael Meeks <[email protected]> ---
Well - the code indeed looks problematic. The issue is that I added this
warning - since the scheduler code is clearly not thread safe, and requires the
SolarMutex - or somesuch to be locked in order to manipulate its structures.
Of course - the timer and idle logic is also really the obvious way to inject
events into the main-loop by people who don't want to hold the solar mutex.
So - quite probably we should introduce a custom lock into the VCL scheduler
and audit it rather carefully for concurrency issues. Clearly we want to hold
the solar mutex over any timer / idle callbacks - but at least pushing events
in there could be improved.
For now - I guess, we could hold the SolarMutex in the AutoRecovery code to
avoid it intermittently corrupting the scheduler's data structures [ not an
ideal outcome ], its the easy fix - but not so satisfying.
Aaron - interested in making the VCL scheduler (+timer+idle+auto-timer)
thread-safe ? hopefully an easy "code-lock" style pattern there (?)
--
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
