Hi Jeremy,
Thanks for reporting that.
Actually I'm not quite sure that drainLoggerRefQueueBounded() needs to
be synchronized on LogManager.
I'll need to study that - but my gut feeling is that we might
be able to get rid of that lock (possibly).
I'll have to study the call chain to see whether t
Anyone else beginning to get the sense that maybe some brainstorming for
a more sweeping/complete change to log manager initialization is
necessary? I suspect that these deadlocks and init order bugs are just
going to keep on coming, and every fix seems to add more complexity than
the last.
