Bug 190492: Crash in OpenCover.Framework.Communication.MessageHandler.StandardMessage

[sawilde]

It looks like the profiler is sending a message that is not known to the host - I suspect a mismatch of profiler and host i.e. the user (for there is only one being recorded) is probably using a new profiler with an older host.

https://drdump.com/Problem.aspx?ProblemID=190492

System.InvalidOperationException: Operation is not valid due to the current state of the object.
 at OpenCover.Framework.Communication.MessageHandler.StandardMessage(MSG_Type msgType, IManagedCommunicationBlock mcb, Action`2 chunkReady, Action`1 offloadHandling) in MessageHandler.cs:112
 at OpenCover.Framework.Communication.CommunicationManager.HandleCommunicationBlock(IManagedCommunicationBlock mcb, Action`1 offloadHandling) in CommunicationManager.cs:60
 at OpenCover.Framework.Manager.ProfilerManager.ProcessMessages(WaitHandle[] handles) in ProfilerManager.cs:233
 at OpenCover.Framework.Manager.ProfilerManager.RunProcess(Action`1 process, String[] servicePrincipal) in ProfilerManager.cs:120
 at OpenCover.Console.Program.RunWithContainer(CommandLineParser parser, Bootstrapper container, IPersistance persistance) in Program.cs:178
 at OpenCover.Console.Program.Main(String[] args) in Program.cs:70

Fix should be in two parts

1. return a different exception that more accurately reports the issue
2. when host/profiler interaction happens there should be a version/compatibility check

[trivalik]

Who is the profiler? What application is her ment? OpenCover itself?

[sawilde]

OpenCover has two main parts - a profiler (written in C++) that interacts with the runtime and a host (written in c#) that collects the data and produces the metrics.