VTune 2019 U1 fails to analyze the data collected by a JIT virtual machine. The application's profiling machinery used to work in several versions of VTune since at least 2017, but for some reason now VTune 2019 U1 fails to finalize the data after the application exits normally. More interestingly, VTune 2018 and 2017 also fail the same way now. This behavior happens consistently on multiple physical machines. Restarting VTune and opening the result causes VTune to try to finalize the result, and again VTune crashes. Different versions of VTune now crash the same way, irrespective of which version is doing the collection.
I had recently updated the VTune SDK, rolling back to a previous version did not fix the problem on multiple VTune versions --- even the ones in which the setup did work.
The crash report notes a multitude of other errors: "we only support MD5 and SHA1 now" (?!), failure to open files, inability to deal with clock tick events, and so on.
Does anyone know what's going on here? That VTune 2019 U1 fails, well ok that may be a problem. But why would older versions of VTune also fail, seemingly just because VTune 2019 U1 is installed?