https://bugs.documentfoundation.org/show_bug.cgi?id=149966
--- Comment #9 from Caolán McNamara <caol...@redhat.com> --- frame #7 and frame #23 both lock the same std::mutex so that's the hang anyway. Trying a std::recursive_mutex as a quick and easy solution doesn't look trivial in this case with the various calls to things that only take std::mutex, alternatively unlocking and relocking before/after elementReplaced etc looks unappealing. -- You are receiving this mail because: You are the assignee for the bug.
