HELP-18938 deals with an infinite recursion. It's hard to diagnose because we only log the boring repetitive top of the stack, not the exciting bottom where the trouble started.

Is it a mistake to truncate the backtrace in deep traces to the 100 top frames like this? I feel like we would be in a better position if we did something to show the bottom of the stack as well.

Maybe we can add auxilliary elements to the "bt" json document to help. Display the 100 bottom frames, which would show where the recursion started, and show how many frames there were in total.