Call tree splitting like URL splitting or method splitting have the potential to create very broad call trees that could use up all available memory. To prevent excessive memory usage, call tree splitting is capped.
After the cap has been reached for a particular splitting type, further splits are consolidated with a description of [capped nodes]. On that node, a hyperlink allows you to reset the cap counter. In that case, new call tree splits will be recorded up to the currently configured cap.