This came out on a local OH users groups on FB where one user noticed his installation hanging from time to time without a clear reason.
The reason was actually quite unexpected: open CLI, run log:tail and select some text in the console window. This makes OH hang as long as the text is selected.
Now, I am sharing this as it is an interesting and unexpected behaviour. It looks like EventLogger implementation of EventSubscriber is blocking the event receive() call on logging. Would that be that Windows implementation of logging is not buffered and can be blocked by simply putting the CMD window to a text mark mode? And this seems to put the whole event dispatch loop on hold, so no state changes can occur during this time.
It seems not a really dangerous case, but something internally is telling me this is just wrong that a user behaviour like that in a totally separated subsystem can actually block the core of another subsystem (e.g. channel state updates).