This will happen when your program closes too soon before the profiler has the opportunity to collect any samples. Perhaps it’s somewhat typical when you kick the tires to see how it works, but you have not written any real code that can be profiled in a meaningful way.
For very short programs with little actual code, be sure to change the profiling mode. Use the Analyze + Performance Wizard and switch from “fetch” to “Instrumentation” mode. Instrumentation mode significantly slows down the program, but is much more accurate for very short programs.
source share