NVVP launch behaviour oddity

Not sure if this is a question on profiling or hardware behaviour, but…

If we launch three identical empty kernels on stream 1, then the runtime API part of the timeline shows three stream creates, three sequential launches, then three stream destroys, and only after that the kernels appear on the compute timeline. What’s going on?