Generally, an erlang supervisor is just waiting for processes to die and react to it; I&#x27;m not sure it makes sense to also have it taking an active interest in processes, but you could quickly build something that periodically calls erlang:process_info&#x2F;2 on all processes, and kills them if they&#x27;re too big (for whatever value of too big).<p>That would get you protection from one process consuming too much ram, and maybe ports (assuming a process is going to link to its ports, you can examine the links), you could also scan ownership of ets tables. You can&#x27;t really track which process is using up all the atoms though.