NullReferenceException when creating log from app

If I open a solution and run it directly from the app, the resulting log file is full of the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Build.Logging.StructuredLogger.ItemGroupParser.ParsePropertyOrItemList(String message, String prefix, StringCache stringTable) in C:\MSBuildStructuredLog\src\StructuredLogger\Construction\ItemGroupParser.cs:line 30
   at Microsoft.Build.Logging.StructuredLogger.MessageProcessor.AddItemGroup(BuildMessageEventArgs args, String prefix, NamedNode containerNode) in C:\MSBuildStructuredLog\src\StructuredLogger\Construction\MessageProcessor.cs:line 154
   at Microsoft.Build.Logging.StructuredLogger.MessageProcessor.Process(BuildMessageEventArgs args) in C:\MSBuildStructuredLog\src\StructuredLogger\Construction\MessageProcessor.cs:line 46
   at Microsoft.Build.Logging.StructuredLogger.Construction.MessageRaised(Object sender, BuildMessageEventArgs args) in C:\MSBuildStructuredLog\src\StructuredLogger\Construction\Construction.cs:line 345

If I use the Build Logging window from inside VS, the resulting log files from the same project appear to be fine.

logs.zip

[KirillOsenkov]

Pushed a new release. Thanks for investigating this!

[bording]

Oh, this is because the exception actually happens inside MSBuild! It’s a different process.

Oh, of course. ItemGroupParser is part of the logger, so that would explain why I wasn’t hitting a breakpoint when opening the log. That would also explain why the binlog from VS didn’t have the problem either.

Could you try with f743ef5 and see if it goes away?

That appears to have fixed it!