After debugging a memory leak in the Xumm backend for the Xumm app, not all debugging settings were reverted after fixing the issue. The memory leak was caused by a third party downstream API serving unexpected large API results without the proper limits in place on the API consuming side.

Due to sticky load balancing, this issue affected 2% of the Xumm user base. The issue was brought to our attention within 2.5 hours & immediately fixed.