leak tracer: poor stack trace performance
Follow-up from !503 (merged):
The elements_leaks
test takes 39 seconds on my (somewhat old) laptop even though it just runs a couple of fakesrc num-buffers=2 ! fakesink
pipelines.
Most of the cpu cycles seems to be spent in libz, related to stack trace management presumably.
Only happens with stack-traces-flags=full
.
Might warrant more investigation. Sure, collecting traces is expensive, but it shouldn't be that expensive.