This is a side effect of #69.
It is possible that the app cannot retrieve XML of an event when the event does not exist actually since EventItem.GetXml() method queries the corresponding event from the system when the user actually clicks on the event.
I encounter this issue when System event log was full and new events came in after opening the app (a rogue service program outputs logs very often on my system).
The app should handle the exception and skip highlighting the (invalid) xml string.
@Ceus , can you support to fix this? You can easily repro if you "Clear Log" on any event log you think is safe to clear after opening the log in the app.
This is a side effect of #69. It is possible that the app cannot retrieve XML of an event when the event does not exist actually since
EventItem.GetXml()
method queries the corresponding event from the system when the user actually clicks on the event. I encounter this issue when System event log was full and new events came in after opening the app (a rogue service program outputs logs very often on my system).The app should handle the exception and skip highlighting the (invalid) xml string.