Comment 15 for bug 1785262

The problem is that thread 1 frame 13 makes a call on a UNO object while it allegedly holds the SolarMutex.

The remote side servicing that call apparently sends back an async release call. However, async calls are executed on fresh threads (thread 6 here), see <https://wiki.openoffice.org/wiki/Uno/Remote/Specifications/Uno_Remote_Protocol#Threads>: "Whenever an asynchronous request message becomes the first entry in a queue for a given TID (of some UNO thread h), the receiving side starts to sequentially execute the computation steps corresponding to the requested UNO interface method, in a new (previously immaterial) thread h′. It uses the TID of thread h′ for all request messages sent while executing these computation steps. When it is finished with the computation steps, thread h′ transitions from active to done, and the asynchronous request message is removed from the head of the queue."