Rising memory load leads to the `interactsh-server` being killed by OOM reaper or VM crash about interactsh HOT 1 OPEN

Thanks for reporting this issue @MMquant - This will be worked on after the final implementation of projectdiscovery/utils#362. Handling this OOM case in interactsh requires some more attention as one of the security requirement is that data should be encrypted and volatile in RAM, so it's indeed more prone to OOM-killing. As a temporary mitigation, while the internal design is being reworked, I would recommend to try with using disk-storage option (that should reduce the pressure on heap) and (if possible) have some swap configured, so that the OS would try to move first some idle memory pages from interactsh process before proceeding to kill it to free memory.

from interactsh.