We've seen occurrences where an unhandled exception cause the default crash dump report to dump call stack, along with the arguments, which potentially can be very large terms (ns_rebalancer_report for example).
Erlang logging framework will attempt to pretty print the large term which will cause a large memory and cpu consumption. It has been observed that when that happen, ns_server becomes unresponsive for long minutes and is not able to process any REST calls.
We can consider number of actions:
1) Further reduce the size and depth
2) Chronicle has customized logging filter to sanitize sensitive information. We can use the same technique to also control terms getting filtered out if they are too large.