You will not see the function call counter in the Timeline / CPU profiler, since the standard profiler in Chrome Dev Tools is a sampler profiler.
The sampler takes snapshots of the execution at a given interval. When this is done, JS execution is paused and functions in the current execution stack are written. This is what you see in the fiery timeline chart.
Given the described behavior, it should be clear that the sampling profiler cannot record all function calls (a function can be called and complete between two measurement pauses).
There are other profilers that can record all function calls, the easiest way to use is perhaps the Web Tracing Framework . It works using your code (rewrite it by wrapping every function call with a measurement code). WTF takes a little longer to set up (instrumentation step) and will affect measured times (as it introduces a new code), but at least it can show all function calls.
The bottom line is that there is not a single profiler that would be ideal for all trace jobs. You have to use different ones, depending on what you want to measure. There is a wonderful conversation in which various profilers are examined in detail, it is highly recommended: https://www.youtube.com/watch?v=nxXkquTPng8
source share