Fixing event logging for the Windows host
The Windows host is supposed to log events using the Windows event logging API so they can be viewed in Event Viewer. During a recent bugfix validation, we discovered that this was broken as no chromoting events were being logged. I tracked down the root cause and it was from a little of 3 years ago: https://chromium-review.googlesource.com/c/chromium/src/+/551035/ In that CL, the HostStatusMonitor functionality was pulled out of the DaemonProcess and put into its own class. The problem was that the observer list was not removed, so instead of using |status_monitor_| to notify listeners, the DaemonProcess continued to use |status_observers_| which is always empty. The fix is to remove the status_observers_ member and notify listeners using the observer list owned by status_monitor_. Bug: 1127439 Change-Id: I9ee00212e0e2c3646ced5711e594a60dfd2627e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406698Reviewed-by:Lambros Lambrou <lambroslambrou@chromium.org> Commit-Queue: Joe Downing <joedow@google.com> Cr-Commit-Position: refs/heads/master@{#806342}
Showing
Please register or sign in to comment