[PATCH v3 0/2] MR3372: ole32: Leave the RunningObjectTable Critical Section before unmarshalling object stream

[Lorenzo Ferrillo (＠llde)]

In certain circumstances unmarshalling an object stream from the RunningObjectTable can cause the unmarshalling routines to interrogate the same 
table (maybe to resolve a dependant object?) in a different thread causing a deadlock while getting the critical section lock. Leaving the Critical Section before unmarshalling the object stream solve this problem.  
Visual Studio 2019 deadlock on start without this.

I'm not sure how to test this properly.
Also add debug info for this critical section so it show a significant name in the log.

Signed-off-by: Lorenzo Ferrillo

--
  v3: ole32: Add debug info to RunningObjectTable critical section

https://gitlab.winehq.org/wine/wine/-/merge_requests/3372