Closed forrestxu123 closed 2 months ago
Please link your trace. This is impossible to debug without it.
There is no limitation on callstack profiling using DISCARD: we use ringbuffer callstack profiling all the time in Google.
IF I USE ringbuffer, I CAN NOT SEE callstack profiling?
Closing as without a trace, this bug cannot be actioned.
Callstack sampling call back works great. but it is only available when buffers: { size_kb: 1522240 fill_policy: DISCARD } buffers: { size_kb: 4096 fill_policy: DISCARD } if fill_policy is set to RING_BUFFER, we can not see Callstack.