[Libreoffice-bugs] [Bug 105062] Firebird: Trying to close Firebird-DB without saving leads to hang of LO
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Mon Oct 16 16:54:28 UTC 2017
https://bugs.documentfoundation.org/show_bug.cgi?id=105062
--- Comment #16 from Jan-Marek Glogowski <glogow at fbihome.de> ---
Created attachment 137017
--> https://bugs.documentfoundation.org/attachment.cgi?id=137017&action=edit
MacOS bt of autorecovery mutex deadlock
Interesting that I couldn't reproduce this on Linux...
So on Mac we have another deadlock on in the DB code:
Two threads wait for mutexes:
* thread #1: tid = 0x18e674, 0x00007fffb17b3c22
libsystem_kernel.dylib`__psynch_mutexwait + 10, queue =
'com.apple.main-thread', stop reason = signal SIGSTOP
thread #5: tid = 0x18e6e7, 0x00007fffb17b3c22
libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'DocumentEventNotifier'
Thread 5 wants the SolarMutex:
frame #5: 0x000000010bd41a69
libvcllo.dylib`SalYieldMutex::doAcquire(this=0x00007fad65c4be00, nLockCount=1)
+ 441 at salinst.cxx:302
(lldb) f 5
....
(lldb) p *this
(SalYieldMutex) $5 = {
comphelper::GenericSolarMutex = {
m_nThreadId = 1631860
$ echo "obase=16; 1631860"|bc
18E674
Which happens to be thread 1.
I can't really verify the mutexes held by thread 5, but my guess it's the one
thread 1 is waiting for.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20171016/4fb7c82b/attachment.html>
More information about the Libreoffice-bugs
mailing list